Tim Abbott | 1 May 01:00 2009
Picon

[PATCH 1/4] alpha: Use macros for .data.page_aligned.

.data.page_aligned should not need a separate output section, so as
part of this cleanup I moved into the .data output section in the
linker scripts in order to eliminate unnecessary references to the
section name.

Signed-off-by: Tim Abbott <tabbott <at> mit.edu>
Cc: Richard Henderson <rth <at> twiddle.net>
Cc: linux-alpha <at> vger.kernel.org
---
 arch/alpha/kernel/vmlinux.lds.S |    6 +-----
 1 files changed, 1 insertions(+), 5 deletions(-)

diff --git a/arch/alpha/kernel/vmlinux.lds.S b/arch/alpha/kernel/vmlinux.lds.S
index b9d6568..2f33cf9 100644
--- a/arch/alpha/kernel/vmlinux.lds.S
+++ b/arch/alpha/kernel/vmlinux.lds.S
 <at>  <at>  -97,11 +97,6  <at>  <at>  SECTIONS
 		*(.data.init_thread)
 	}

-	. = ALIGN(PAGE_SIZE);
-	.data.page_aligned : {
-		*(.data.page_aligned)
-	}
-
 	. = ALIGN(64);
 	.data.cacheline_aligned : {
 		*(.data.cacheline_aligned)
 <at>  <at>  -110,6 +105,7  <at>  <at>  SECTIONS
 	_data = .;
(Continue reading)

Oliver Neukum | 1 May 01:02 2009

Re: What's in hid.git for 2.6.30

Am Freitag, 1. Mai 2009 00:45:51 schrieb Jiri Kosina:
> --- a/drivers/hid/hid-core.c
> +++ b/drivers/hid/hid-core.c
>  <at>  <at>  -1824,6 +1824,9  <at>  <at>  int hid_check_keys_pressed(struct hid_device *hid)
>         struct hid_input *hidinput;
>         int i;
>  
> +       if (!(hid->claimed & HID_CLAIMED_INPUT))
> +               return 0;
> +

Jiri,

is there a guarantee all keyboards will be claimed as input devices?

	Regards
		Oliver

Tim Abbott | 1 May 01:00 2009
Picon

[PATCH 2/4] alpha: use new macro for .data.cacheline_aligned section.

.data.cacheline_aligned should not need a separate output section;
this change moves it into the .data section.

Signed-off-by: Tim Abbott <tabbott <at> mit.edu>
Cc: Richard Henderson <rth <at> twiddle.net>
Cc: linux-alpha <at> vger.kernel.org
---
 arch/alpha/kernel/vmlinux.lds.S |    6 +-----
 1 files changed, 1 insertions(+), 5 deletions(-)

diff --git a/arch/alpha/kernel/vmlinux.lds.S b/arch/alpha/kernel/vmlinux.lds.S
index 2f33cf9..7acd1eb 100644
--- a/arch/alpha/kernel/vmlinux.lds.S
+++ b/arch/alpha/kernel/vmlinux.lds.S
 <at>  <at>  -97,15 +97,11  <at>  <at>  SECTIONS
 		*(.data.init_thread)
 	}

-	. = ALIGN(64);
-	.data.cacheline_aligned : {
-		*(.data.cacheline_aligned)
-	}
-
 	_data = .;
 	/* Data */
 	.data : {
 		PAGE_ALIGNED_DATA
+		CACHELINE_ALIGNED_DATA(64)
 		DATA_DATA
 		CONSTRUCTORS
(Continue reading)

Tim Abbott | 1 May 01:00 2009
Picon

[PATCH 3/4] alpha: make THREAD_SIZE available to assembly files.

This allows THREAD_SIZE to be used in the linker script.

Signed-off-by: Tim Abbott <tabbott <at> mit.edu>
Cc: Richard Henderson <rth <at> twiddle.net>
Cc: linux-alpha <at> vger.kernel.org
---
 arch/alpha/include/asm/thread_info.h |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/alpha/include/asm/thread_info.h b/arch/alpha/include/asm/thread_info.h
index d069526..a64d74d 100644
--- a/arch/alpha/include/asm/thread_info.h
+++ b/arch/alpha/include/asm/thread_info.h
 <at>  <at>  -49,12 +49,12  <at>  <at>  struct thread_info {
 register struct thread_info *__current_thread_info __asm__("$8");
 #define current_thread_info()  __current_thread_info

+#endif /* __ASSEMBLY__ */
+
 /* Thread information allocation.  */
 #define THREAD_SIZE_ORDER 1
 #define THREAD_SIZE (2*PAGE_SIZE)

-#endif /* __ASSEMBLY__ */
-
 #define PREEMPT_ACTIVE		0x40000000

 /*
--

-- 
1.6.2.1
(Continue reading)

Tim Abbott | 1 May 01:00 2009
Picon

[PATCH 0/4] section name cleanup for alpha

This patch series cleans up the section names on the alpha
architecture.  It requires the architecture-independent macro
definitions from this patch series:

<http://www.spinics.net/lists/mips/msg33499.html>

The long-term goal here is to add support for building the kernel with
-ffunction-sections -fdata-sections.  This requires renaming all the
magic section names in the kernel of the form .text.foo, .data.foo,
.bss.foo, and .rodata.foo to not have collisions with sections
generated for code like:

static int nosave = 0; /* -fdata-sections places in .data.nosave */
static void head(); /* -ffunction-sections places in .text.head */

Note that these patches have not been boot-tested (aside from testing
the analogous changes on x86), since I don't have access to the
appropriate hardware.

	-Tim Abbott

Tim Abbott (4):
  alpha: Use macros for .data.page_aligned.
  alpha: use new macro for .data.cacheline_aligned section.
  alpha: make THREAD_SIZE available to assembly files.
  alpha: use .data.init_task instead of .data.init_thread

 arch/alpha/include/asm/thread_info.h |    4 ++--
 arch/alpha/kernel/init_task.c        |    5 ++---
 arch/alpha/kernel/vmlinux.lds.S      |   19 ++++---------------
(Continue reading)

Tim Abbott | 1 May 01:00 2009
Picon

[PATCH 4/4] alpha: use .data.init_task instead of .data.init_thread

alpha is the only architecture that uses the section name
.data.init_thread instead of .data.init_task.  So convert alpha to use
.data.init_task like everything else.

.data.init_task should not need a separate output section; this change
also moves it into the .data output section.

Signed-off-by: Tim Abbott <tabbott <at> mit.edu>
Cc: Richard Henderson <rth <at> twiddle.net>
Cc: linux-alpha <at> vger.kernel.org
---
 arch/alpha/kernel/init_task.c   |    5 ++---
 arch/alpha/kernel/vmlinux.lds.S |    7 ++-----
 2 files changed, 4 insertions(+), 8 deletions(-)

diff --git a/arch/alpha/kernel/init_task.c b/arch/alpha/kernel/init_task.c
index c2938e5..475d46a 100644
--- a/arch/alpha/kernel/init_task.c
+++ b/arch/alpha/kernel/init_task.c
 <at>  <at>  -16,6 +16,5  <at>  <at>  struct task_struct init_task = INIT_TASK(init_task);
 EXPORT_SYMBOL(init_mm);
 EXPORT_SYMBOL(init_task);

-union thread_union init_thread_union
-	__attribute__((section(".data.init_thread")))
-	= { INIT_THREAD_INFO(init_task) };
+union thread_union init_thread_union __init_task_data =
+	{ INIT_THREAD_INFO(init_task) };
diff --git a/arch/alpha/kernel/vmlinux.lds.S b/arch/alpha/kernel/vmlinux.lds.S
index 7acd1eb..caca724 100644
(Continue reading)

Jiri Kosina | 1 May 01:09 2009
Picon

Re: What's in hid.git for 2.6.30

On Fri, 1 May 2009, Oliver Neukum wrote:

> > --- a/drivers/hid/hid-core.c
> > +++ b/drivers/hid/hid-core.c
> >  <at>  <at>  -1824,6 +1824,9  <at>  <at>  int hid_check_keys_pressed(struct hid_device *hid)
> >         struct hid_input *hidinput;
> >         int i;
> >  
> > +       if (!(hid->claimed & HID_CLAIMED_INPUT))
> > +               return 0;
> > +
> is there a guarantee all keyboards will be claimed as input devices?

Hi Oliver,

do you see any way how hid->inputs could currently be initialized other 
than the device being claimed by hid-input?

--

-- 
Jiri Kosina
SUSE Labs
David Rees | 1 May 01:17 2009
Picon

Re: Slow clock on AMD 740G chipset

On Fri, Apr 24, 2009 at 6:45 PM, David Rees <drees76 <at> gmail.com> wrote:
> On Tue, Mar 24, 2009 at 10:34 AM, Michael Tokarev <mjt <at> tls.msk.ru> wrote:
>> To refresh what has been said.  Several people observed slow clock
>> on their - mostly AMD 780g, 740g and 690g-based systems with 2.6.28
>> 2.6.27 kernels.  Slow to a point when ntpd wasn't successful to
>> keep up with the drift.  It has been said that the motherboards are
>> flaky or something and that the clocks has to be calibrated, for
>> which there are known procedures available (adjtimex).  Which helped.
>> Before the "calibration" the clock were off by ~15 minutes per day.
>
> This is really weird.  I earlier posted to the thread saying things
> were fine on a Fedora 10 2.6.27.9-159.fc10.x86_64 kernel.
>
> Then mysteriously after a machine reboot to install new hardware[1] on
> March 27th on kernel 2.6.27.19-170.2.35.fc10.x86_64 (previous running
> kernel was the same), the clock started running slow to the tune of
> ntpd resetting the time every 15-18 minutes forward about 2.3 seconds.
>
> Fast forward to today (now running 2.6.29.1-30.fc10.x86_64) and the
> clock is still running slow.
>
> I don't know - my system (GA-MA74GM-S2 mobo) is still broken.
>
> [1] So the hardware I installed was a SATA SSD (OCZ Vertex). Ever
> since then, the clock has been running fast.  Previously, the only
> thing on the SATA bus was a DVD drive - it has two IDE drives, one
> plugged in on board and the other into a Promise IDE card.
>
> When doing so, the sata ports are now running in AHCI mode instead of
> native mode.  I'll have to try switching later.
(Continue reading)

Andrew Morton | 1 May 01:29 2009

Re: [PATCH] Intel IOMMU Pass Through Support

On Wed, 15 Apr 2009 17:19:57 -0700
Fenghua Yu <fenghua.yu <at> intel.com> wrote:

> The patch adds kernel parameter intel_iommu=pt to set up pass through mode in
> context mapping entry. This disables DMAR in linux kernel; but KVM still runs on
> VT-d and interrupt remapping still works.
> 
> In this mode, kernel uses swiotlb for DMA API functions but other VT-d
> functionalities are enabled for KVM. KVM always uses multi level translation
> page table in VT-d. By default, pass though mode is disabled in kernel.
> 
> This is useful when people don't want to enable VT-d DMAR in kernel but still
> want to use KVM and interrupt remapping for reasons like DMAR performance
> concern or debug purpose.
> 

The patch is now in linux-next and broke my build.

arch/x86/built-in.o: In function `iommu_setup':
arch/x86/kernel/pci-dma.c:215: undefined reference to `iommu_pass_through'
arch/x86/built-in.o: In function `pci_swiotlb_init':
arch/x86/kernel/pci-swiotlb.c:74: undefined reference to `iommu_pass_through'

Because iommu_pass_through is defined in drivers/pci/intel-iommu.c and

# CONFIG_DMAR is not set

I'll need to cook up some local hack to work around that.

Also, the patch in linux-next (but not the one which I'm replying to
(Continue reading)

Randy Dunlap | 1 May 01:37 2009
Picon

Re: [PATCH] Intel IOMMU Pass Through Support

Andrew Morton wrote:
> On Wed, 15 Apr 2009 17:19:57 -0700
> Fenghua Yu <fenghua.yu <at> intel.com> wrote:
> 
>> The patch adds kernel parameter intel_iommu=pt to set up pass through mode in
>> context mapping entry. This disables DMAR in linux kernel; but KVM still runs on
>> VT-d and interrupt remapping still works.
>>
>> In this mode, kernel uses swiotlb for DMA API functions but other VT-d
>> functionalities are enabled for KVM. KVM always uses multi level translation
>> page table in VT-d. By default, pass though mode is disabled in kernel.
>>
>> This is useful when people don't want to enable VT-d DMAR in kernel but still
>> want to use KVM and interrupt remapping for reasons like DMAR performance
>> concern or debug purpose.
>>
> 
> The patch is now in linux-next and broke my build.
> 
> arch/x86/built-in.o: In function `iommu_setup':
> arch/x86/kernel/pci-dma.c:215: undefined reference to `iommu_pass_through'
> arch/x86/built-in.o: In function `pci_swiotlb_init':
> arch/x86/kernel/pci-swiotlb.c:74: undefined reference to `iommu_pass_through'
> 
> Because iommu_pass_through is defined in drivers/pci/intel-iommu.c and
> 
> # CONFIG_DMAR is not set
> 
> I'll need to cook up some local hack to work around that.
> 
(Continue reading)


Gmane