On Sat, 2007-11-17 at 18:46 +0100, Ingo Molnar wrote:
> fixing the top 20:
>
There are about 25 DECLARE_MUTEX() semaphores remaining .. One is the
BKL which I would guess can't be converted. The others I've looked at
appear to be trivial find/replace changes to get them to use the mutex
type..
On Tue, 2007-11-20 at 15:31 +0100, Rene Herman wrote:
> On 20-11-07 15:19, Thomas Renninger wrote:
>
> > At the end is some example code how things could get even more cleaned
> > up. It shows how I think pnp layer and one example driver would get
> > adjusted. There are not that much drivers
On Wed 21-11-07 00:40:17, Coly Li wrote:
> Jan Kara wrote:
> >> diff --git a/fs/ext4/ialloc.c b/fs/ext4/ialloc.c
> >> index 17b5df1..f838a72 100644
> >> --- a/fs/ext4/ialloc.c
> >> +++ b/fs/ext4/ialloc.c
> >> @@ -10,6 +10,8 @@
> >> * Stephen Tweedie ([EMAIL PROTECTED]), 1993
> >> *
Hi,
Here you can find some performance comparison in terms of CPU
utilization and transactions per second (using FFSB) on ext4 filesystem
with and without i_version option.
http://bullopensource.org/ext4/20071116/ffsb-write.html
regards,
Jean noel
-
To unsubscribe from this list: send the
On Tue, 20 Nov 2007 14:52:37 +
Dean Jenkins <[EMAIL PROTECTED]> wrote:
> Hi Pierre,
>
> My card driver needed to set the R/W E4MI bit in the Card Capability
> register (0x08) in CCCR (function 0). Perhaps it is unnecessary ?
>
That bit is pointless given the current design of the MMC
The hearburn I have with these patches is that you are changing driver-specific
attributes, not common ones as enforced/requested by a subsystem. As such, you
are breaking a management interface for existing tools/scripts.
There's been a long-standing request to create common device attributes,
On 11/19, Eric W. Biederman wrote:
>
> So to fix the problem this patch modifies next_tgid() to return
> both a tgid and the task struct in question.
>
> A structure is introduced to return these values because it is
> slightly cleaner and easier to optimize, and the resulting code
> is a little
Jan,
Thanks for taking time to review the patch :-)
Jan Kara wrote:
> Hi Coly,
>
> finally I've found some time to have a look at a new version of your
> patch.
>
>> 5, Performance number
>> On a Core-Duo, 2MB DDM memory, 7200 RPM SATA PC, I built a 50GB ext4
>> partition, and tried to
This patch adds extended interrupt support for AMD Barcelona CPUs. The
patch provides functions to setup MCE and IBS interrupt
vectors. Compared to the previous K8 implementation the vector offsets
are centrally handled now in apic_64.c. Thus, the APIC setup code is
responsible for vector
Fix arp reply when received arp probe with sender ip 0.
Send arp reply with target ip address 0.0.0.0 and target hardware address
set to hardware address of requester. Previously sent reply with target
ip address and target hardware address set to same as source fields.
Signed-off-by: Jonas
On Mon, 19 Nov 2007, Alex Chiang wrote:
> Ugh, seems that stacked git got very confused when I did a
> git-fetch && git-rebase origin. Also, guess it figures that I
Being a very heavy stgit user myself, I have to say you must give up git
rebase on any stgit branch, and use stg rebase instead...
On (20/11/07 10:14), Lee Schermerhorn didst pronounce:
> On Tue, 2007-11-20 at 14:19 +, Mel Gorman wrote:
> > On (09/11/07 07:45), Christoph Lameter didst pronounce:
> > > On Fri, 9 Nov 2007, Mel Gorman wrote:
> > >
> > > > struct page * fastcall
> > > > __alloc_pages(gfp_t gfp_mask,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
dean gaudet wrote:
> as an application writer how do i access accept(2) with FD_CLOEXEC
> functionality? will glibc expose an accept2() with a flags param?
Not yet decided. There is the alternative to extend the accept()
interface to have both
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Heiko Carstens wrote:
> All these macros could be functions, or? Would give us some type checking
> and avoids the capital letters.
Should be possible now. I didn't do it initially since the macro used
the macro for the largest syscall number. That
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Dumazet wrote:
> I am wondering if some parts are missing from your ChangeLog
>
> You apparently added in v3 a new 'flags' parameter to indirect syscall
> but no trace of this change in Changelog, and why it was added. This
> seems to imply a
Anthony Liguori wrote:
Avi Kivity wrote:
Anthony Liguori wrote:
This is a PCI device that implements a transport for virtio. It
allows virtio
devices to be used by QEMU based VMMs like KVM or Xen.
+
+/* the notify function used when creating a virt queue */
+static void
Arjan van de Ven wrote:
On Tue, 20 Nov 2007 10:52:48 -0500
Mark Lord <[EMAIL PROTECTED]> wro
All of which reminds me of perhaps *the* most important reason to keep
core functionality like "IRQ distribution" *inside* the kernel:
It has to pass peer review on this mailing list.
that's a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Miller wrote:
> FWIW, I think this indirect syscall stuff is the most ugly interface
> I've ever seen proposed for the kernel.
Well, the alternative is to introduce a dozens of new interfaces. It
was Linus who suggested this alternative.
On Tue, 20 Nov 2007 10:52:48 -0500
Mark Lord <[EMAIL PROTECTED]> wro
>
> All of which reminds me of perhaps *the* most important reason to keep
> core functionality like "IRQ distribution" *inside* the kernel:
>
>It has to pass peer review on this mailing list.
that's a reason to keep it
On Wednesday 21 November 2007 01:47, Arjan van de Ven wrote:
> On Tue, 20 Nov 2007 18:37:39 +1100
>
> Nick Piggin <[EMAIL PROTECTED]> wrote:
> > > actually no. IRQ balancing is not a "fast" decision; every time
> > > you
> >
> > I didn't say anything of the sort. But IRQ load could still
Hi Coly,
finally I've found some time to have a look at a new version of your
patch.
> 5, Performance number
> On a Core-Duo, 2MB DDM memory, 7200 RPM SATA PC, I built a 50GB ext4
> partition, and tried to create 5 directories, and create 15 (1KB)
> files in each directory alternatively.
> >and it seems like this patch and perfmon2 are going to have to
> >live with
> >each other... since they both require the use of the DS save area...
>
> Hmmm, this might require some synchronization between those two.
>
> Do you know how (accesses to) MSR's are managed by the kernel?
There
Mark Lord wrote:
Arjan van de Ven wrote:
..
I listed a few;
1) it's policy 2) the memory is only needed for a short time (20
seconds or so) on
single-socket machines
3) it makes decisions on "subjective" information such as interrupt
device classes that the kernel currently just doesn't have
Rafael J. Wysocki wrote:
> On Monday, 19 of November 2007, Pavel Machek wrote:
>> Hi!
>>
>> I think that this worked before:
>>
>> [EMAIL PROTECTED]:/proc# find . -name "timer_info"
>> find: WARNING: Hard link count is wrong for ./net: this may be a bug
>> in your filesystem driver. Automatically
>-Original Message-
>From: dean gaudet [mailto:[EMAIL PROTECTED]
>Sent: Dienstag, 20. November 2007 16:37
>To: Metzger, Markus T
>Cc: linux-kernel@vger.kernel.org; [EMAIL PROTECTED];
>[EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Siddha, Suresh
>B; [EMAIL PROTECTED]
> We might want to add support for Netburst in 64bit mode some day.
> For today, I simply exclude Netburst for x86_64.
If you switched to table driven then adding another format like
this would be likely very easy. It's just that with the "own code for
everything"
method it becomes difficult.
Network state machine.
Includes network async processing state machine and related tasks.
Signed-off-by: Evgeniy Polyakov <[EMAIL PROTECTED]>
diff --git a/drivers/block/dst/kst.c b/drivers/block/dst/kst.c
new file mode 100644
index 000..ba5e5ef
--- /dev/null
+++ b/drivers/block/dst/kst.c
Arjan van de Ven wrote:
..
I listed a few;
1) it's policy
2) the memory is only needed for a short time (20 seconds or so) on
single-socket machines
3) it makes decisions on "subjective" information such as interrupt
device classes that the kernel currently just doesn't have (it could
grow
Avi Kivity wrote:
Anthony Liguori wrote:
This is a PCI device that implements a transport for virtio. It
allows virtio
devices to be used by QEMU based VMMs like KVM or Xen.
+
+/* the notify function used when creating a virt queue */
+static void vp_notify(struct virtqueue *vq)
+{
+
On Fri, 2007-11-09 at 14:33 +, Mel Gorman wrote:
> Filtering zonelists requires very frequent use of zone_idx(). This is costly
> as it involves a lookup of another structure and a substraction operation. As
> the zone_idx is often required, it should be quickly accessible. The node
> idx
Algorithms used in distributed storage.
Mirror and linear mapping code.
Signed-off-by: Evgeniy Polyakov <[EMAIL PROTECTED]>
diff --git a/drivers/block/dst/alg_linear.c b/drivers/block/dst/alg_linear.c
new file mode 100644
index 000..cb77b57
--- /dev/null
+++
Distributed storage.
I'm pleased to announce the 8'th release of the distributed
storage subsystem (DST). This is a maintenance release and includes
bug fixes only.
DST allows to form a storage on top of local and remote nodes
and combine them into linear or mirroring setup, which in
turn can
Core distributed storage files.
Include userspace interfaces, initialization,
block layer bindings and other core functionality.
Signed-off-by: Evgeniy Polyakov <[EMAIL PROTECTED]>
diff --git a/drivers/block/Kconfig b/drivers/block/Kconfig
index b4c8319..ca6592d 100644
---
Distributed storage documentation.
Algorithms used in the system, userspace interfaces
(sysfs dirs and files), design and implementation details
are described here.
Signed-off-by: Evgeniy Polyakov <[EMAIL PROTECTED]>
diff --git a/Documentation/dst/algorithms.txt
>-Original Message-
>From: dean gaudet [mailto:[EMAIL PROTECTED]
>Sent: Dienstag, 20. November 2007 16:27
>To: Metzger, Markus T
>Cc: linux-kernel@vger.kernel.org; [EMAIL PROTECTED];
>[EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; Siddha, Suresh
>B; [EMAIL PROTECTED]
On Tue, 20 Nov 2007, dean gaudet wrote:
> On Tue, 20 Nov 2007, Metzger, Markus T wrote:
>
> > +__cpuinit void ptrace_bts_init_intel(struct cpuinfo_x86 *c)
> > +{
> > + switch (c->x86) {
> > + case 0x6:
> > + switch (c->x86_model) {
> > +#ifdef __i386__
> > + case 0xD:
> >
Minor cleanup. We can remove one "else if" branch.
Signed-off-by: Oleg Nesterov <[EMAIL PROTECTED]>
--- PT/kernel/exit.c~3_EXIT_DEAD2007-11-20 17:54:07.0 +0300
+++ PT/kernel/exit.c2007-11-20 18:23:16.0 +0300
@@ -1561,8 +1561,6 @@ repeat:
On Tue, 2007-11-20 at 15:17 +, Christoph Hellwig wrote:
> On Tue, Nov 20, 2007 at 10:05:05AM -0500, Stephen Smalley wrote:
> > > Nice, getting rid of this is a very good step formwards. Unfortunately
> > > we have another copy of this junk in
> > >
On Tuesday 20 November 2007 02:11:33 [EMAIL PROTECTED] wrote:
> ACPI uses NR_CPUS in various loops and in some it accesses per cpu
> data of processors that are not present(!) and that will never be present.
> The pointers to per cpu data are typically not initialized for processors
> that are not
On Tue, 20 Nov 2007, Metzger, Markus T wrote:
> +__cpuinit void ptrace_bts_init_intel(struct cpuinfo_x86 *c)
> +{
> + switch (c->x86) {
> + case 0x6:
> + switch (c->x86_model) {
> +#ifdef __i386__
> + case 0xD:
> + case 0xE: /* Pentium M */
> +
On 19/11/07 18:58 -0800, Joe Perches wrote:
> On Mon, 2007-11-19 at 18:54 -0700, [EMAIL PROTECTED]
> wrote:
> > You are not allowed to post to this mailing list, and your message has
> > been automatically rejected. If you think that your messages are
> > being rejected in error, contact the
Now that my_ptrace_child() is trivial we can use the "p->ptrace & PT_PTRACED"
inline and simplify the corresponding logic in do_wait: we can't find the child
in TASK_TRACED state without PT_PTRACED flag set, ptrace_untrace() either sets
TASK_STOPPED or wakes up the tracee.
Signed-off-by: Oleg
On Tue, 2007-11-20 at 14:19 +, Mel Gorman wrote:
> On (09/11/07 07:45), Christoph Lameter didst pronounce:
> > On Fri, 9 Nov 2007, Mel Gorman wrote:
> >
> > > struct page * fastcall
> > > __alloc_pages(gfp_t gfp_mask, unsigned int order,
> > > struct zonelist *zonelist)
> > > {
>
Since the patch
"Fix ptrace_attach()/ptrace_traceme()/de_thread() race"
commit f5b40e363ad6041a96e3da32281d8faa191597b9
we set PT_ATTACHED and change child->parent "atomically" wrt task_list lock.
This means we can remove the checks like "PT_ATTACHED && ->parent != ptracer"
Hi David,
On Sat, 17 Nov 2007 09:36:24 -0800, David Brownell wrote:
> On Saturday 17 November 2007, Jean Delvare wrote:
> > On Tue, 13 Nov 2007 20:36:13 -0800, David Brownell wrote:
> > > On Tuesday 13 November 2007, eric miao wrote:
> > > > if (!requested)
> > > > -
On Tue, Nov 20, 2007 at 10:05:05AM -0500, Stephen Smalley wrote:
> > Nice, getting rid of this is a very good step formwards. Unfortunately
> > we have another copy of this junk in
> > security/selinux/selinuxfs.c:sel_remove_entries() which would need the
> > same treatment.
>
> Can't just be
Hi Andrew,
The kernel build fails, on the AMD machine with following message
arch/x86/ia32/ia32_aout.c: In function ‘load_aout_binary’:
arch/x86/ia32/ia32_aout.c:283: error: implicit declaration of function ‘N_MAGIC’
arch/x86/ia32/ia32_aout.c:283: error: ‘ZMAGIC’ undeclared (first use in this
> At the end is some example code how things could get even more cleaned
> up. It shows how I think pnp layer and one example driver would get
Your example adds rather than removes code.
> If this is not an option, please advise how to move on here:
> Still use struct resources for dma and irq,
On Tue, 2007-11-20 at 10:39 +, Alistair John Strachan wrote:
> On Tuesday 20 November 2007 01:53:31 Joe Perches wrote:
> > diff --git a/drivers/scsi/NCR_D700.c b/drivers/scsi/NCR_D700.c
> > index 9e64b21..99403a6 100644
> > --- a/drivers/scsi/NCR_D700.c
> > +++ b/drivers/scsi/NCR_D700.c
> > @@
Hi,
I've got some semi-embedded device here, a plain consumer-grade x86 with
a VIA Nehemiah/Eden C7. After a while it just locks up, but neither is
that deterministic nor does it give out kernel messages. CPU Frequency
Scaling (which has been known to be a problem with this CPU) is already
On Mon, 2007-11-19 at 12:51 +, Christoph Hellwig wrote:
> On Fri, Nov 16, 2007 at 06:06:51PM +0300, Alexey Dobriyan wrote:
> > proc_kill_inodes() can clear ->i_fop in the middle of vfs_readdir resulting
> > in
> > NULL dereference during "file->f_op->readdir(file, buf, filler)".
> >
> > The
Anthony Liguori wrote:
This is a PCI device that implements a transport for virtio. It allows virtio
devices to be used by QEMU based VMMs like KVM or Xen.
+
+/* the notify function used when creating a virt queue */
+static void vp_notify(struct virtqueue *vq)
+{
+ struct
On Tue, 20 Nov 2007, Huang, Ying wrote:
> - What is the difference between PMSG_SUSPEND and PMSG_FREEZE?
SUSPEND means that the system is about to go into a low-power state, so
the driver should take the appropriate action to reduce the device's
power consumption. It should also stop all I/O
On Tue, 20 Nov 2007 11:14:59 +0100
Mikael Ståldal <[EMAIL PROTECTED]> wrote:
> In Linux you have to be root in order to listen to TCP or UDP ports below
> 1024 (the
> well-known ports). As far as I know, this limit is hardcoded in the kernel.
>
> In some cases, this limit do more harm than
Hello,
I have laptop thinkpad T61 with 82566MM Gigabit Network Connection (rev 03)
(8086:1049). I have kernel 2.6.24-rc3. E1000E driver does not work (the card
is not detected although it is PCI-E), with E1000 driver, it works mostly OK
unless I force speed to 100Mbits. (ethtool -s eth0 autoneg
Hi Pierre,
My card driver needed to set the R/W E4MI bit in the Card Capability
register (0x08) in CCCR (function 0). Perhaps it is unnecessary ?
BTW. It is easy to for the card driver to access function 0 registers by
doing the following...
...
int old_num = func->num; /* note the
Quoting Chris Friedhoff ([EMAIL PROTECTED]):
> On Mon, 19 Nov 2007 17:16:44 -0600
> "Serge E. Hallyn" <[EMAIL PROTECTED]> wrote:
>
> > Quoting Chris Friedhoff ([EMAIL PROTECTED]):
> > > Hello Serge,
> > >
> > > just to let you know: with 2.6.24-rc3 I have the same problem.
> >
> > Ok, so here
Hi Andrew,
The kernel build fails, with foloowing message,
CC arch/x86/kernel/pci-gart_64.o
arch/x86/kernel/pci-gart_64.c: In function ‘gart_map_sg’:
arch/x86/kernel/pci-gart_64.c:421: error: redeclaration of ‘s’ with no linkage
arch/x86/kernel/pci-gart_64.c:416: error: previous
On Tue, 20 Nov 2007 18:37:39 +1100
Nick Piggin <[EMAIL PROTECTED]> wrote:
> > actually no. IRQ balancing is not a "fast" decision; every time
> > you
>
> I didn't say anything of the sort. But IRQ load could still fluctuate
> a lot more rapidly than we'd like to wake up the irqbalancer.
irq
I have one powerpc machine which managed to compile this snapshot! It
paniced on boot as below, might be nfs so copied them. General results
are popping out on TKO.
-apw
Freeing initrd memory: 1224k freed
Installing knfsd (copyright (C) 1996 [EMAIL PROTECTED]).
Unable to handle kernel paging
Torsten Kaiser wrote:
> On Nov 19, 2007 10:00 PM, Milan Broz <[EMAIL PROTECTED]> wrote:
>> Torsten Kaiser wrote:
>>> Anything I could try, apart from more boots with slub_debug=F?
>
> One time it triggered with slub_debug=F, but no additional output.
> With slub_debug=FP I have not seen it again,
On 20-11-07 15:19, Thomas Renninger wrote:
At the end is some example code how things could get even more cleaned
up. It shows how I think pnp layer and one example driver would get
adjusted. There are not that much drivers making use of
pnp_resource_change...
The ALSA ISA-PnP drivers do in
On Tue, 2007-11-20 at 09:29 +0100, Thomas Bogendoerfer wrote:
> On Tue, Nov 20, 2007 at 06:51:14AM +1100, Benjamin Herrenschmidt wrote:
> >
> > On Mon, 2007-11-19 at 00:38 -0800, David Miller wrote:
> > > From: Benjamin Herrenschmidt <[EMAIL PROTECTED]>
> > > Date: Mon, 19 Nov 2007 16:35:23
Good morning to everyone.
I'm working to sort out what appear to be issues with binding of the
serial_cs driver to a PCMCIA wireless card (Zoom).
Card works perfectly in recent 2.6.2[23] kernels if cardmgr is running
and PCMCIA_IOCTL support is in the kernel. The serial_cs driver
fails,
On Tue, Nov 20, 2007 at 03:21:38PM +0100, Thomas Gleixner wrote:
> On Tue, 20 Nov 2007, Thomas Gleixner wrote:
> > > arch/x86/kernel/setup_64.c:991: error: redefinition of ‘identify_cpu’
> > > arch/x86/kernel/setup_64.c:958: error: previous definition of
> > > ‘identify_cpu’ was here
> > >
>-Original Message-
>From: Harald Dunkel [mailto:[EMAIL PROTECTED]
>Sent: Tuesday, November 20, 2007 12:17 AM
>To: Pallipadi, Venkatesh
>Cc: Linux Kernel list
>Subject: Re: 2.6.23.8, ondemand scaling governor: "BUG: soft
>lockup detected on CPU#0!"
>
>Pallipadi, Venkatesh wrote:
>>
Hi Andrew,
The kernel build fails, on one of the machine
CC arch/x86/mach-generic/summit.o
In file included from arch/x86/mach-generic/summit.c:16:
include/asm/mach-summit/mach_apic.h: In function ‘target_cpus’:
include/asm/mach-summit/mach_apic.h:23: error: ‘per_cpu__cpu_mask’
On Tue, 20 Nov 2007, Thomas Gleixner wrote:
> > arch/x86/kernel/setup_64.c:991: error: redefinition of ‘identify_cpu’
> > arch/x86/kernel/setup_64.c:958: error: previous definition of
> > ‘identify_cpu’ was here
> > make[1]: *** [arch/x86/kernel/setup_64.o] Error 1
> > make: *** [arch/x86/kernel]
On (09/11/07 07:45), Christoph Lameter didst pronounce:
> On Fri, 9 Nov 2007, Mel Gorman wrote:
>
> > struct page * fastcall
> > __alloc_pages(gfp_t gfp_mask, unsigned int order,
> > struct zonelist *zonelist)
> > {
> > + /*
> > +* Use a temporary nodemask for __GFP_THISNODE
On Tue, 2007-11-20 at 12:31 +, Alan Cox wrote:
> On Tue, 20 Nov 2007 10:51:23 +0100
> Thomas Renninger <[EMAIL PROTECTED]> wrote:
>
> > Unify the pnp macros to access resources in the pnp resource table
>
> NAK
>
> > port, mem, dma and irq resource macros are now all used in the same
> >
Hi,
I see gitweb is much more usable (faster) than a few months ago, but
there is one thing a bit problematic: in the history of patches I'm
very often interested in which kernel version of Linus' tree the patch
appeared for the first time. If it's not some big problem, and maybe
somebody else
At Tue, 20 Nov 2007 19:32:49 +0530,
Kamalesh Babulal wrote:
>
> Hi Andrew,
>
> The kernel build fails, with following error
>
> CC sound/ppc/tumbler.o
> sound/ppc/tumbler.c: In function ‘snapper_get_capture_source’:
> sound/ppc/tumbler.c:812: error: ‘union ’ has no member named
>
On Mon, 19 Nov 2007, Ingo Molnar wrote:
>
> * Eric Dumazet <[EMAIL PROTECTED]> wrote:
>
> > I do see a problem, because some readers will take your example as a
> > reference, as it will probably sit in a page that
> > google^Wsearch_engines will bring at the top of search results for
> >
On Tue, 20 Nov 2007 12:26:11 +
Dean Jenkins <[EMAIL PROTECTED]> wrote:
> Hi Pierre,
>
> IMHO the issue is there is no upper bound limit to the valid address
> range in sdio_io_rw_ext_helper() in sdio_io.c.
>
> I call sdio_memcpy_toio() as it enables the incrementing address flag in
> the
>> my HP 385 G2 - 2x dual core Opteron 2216 running 2.6.23.1 with NUMA support
>> says the following:
>
> Can you post a full boot log?
Here it is.
Further I have a problem with booting the kernel on 4x dual core Opteron
(HP585). It prints lot of panics on boot to console but not to the log.
Hi Andrew,
The kernel build fails, with following error
CC sound/ppc/tumbler.o
sound/ppc/tumbler.c: In function ‘snapper_get_capture_source’:
sound/ppc/tumbler.c:812: error: ‘union ’ has no member named ‘value’
sound/ppc/tumbler.c: In function ‘snapper_put_capture_source’:
Hi:
[KERNEL]: Avoid divide in IS_ALIGN
I was happy to discover the brand new IS_ALIGN macro and quickly
used it in my code. To my dismay I found that the generated code
used division to perform the test.
This patch fixes it by changing the % test to an &. This avoids
the division.
From: Corey Minyard <[EMAIL PROTECTED]>
Add the standard IOCTLs to the IPMI driver for setting and getting
the pretimeout. Tested by Benoît Guillon.
Signed off by: Corey Minyard <[EMAIL PROTECTED]>
Cc: Benoît Guillon <[EMAIL PROTECTED]>
---
Index: linux-2.6.23/drivers/char/ipmi/ipmi_watchdog.c
Looking around sysfs in an attempt to pull out SCSI card firmware
versions I found 5 different filenames used to store the information.
Only one, fw_version, was used more than once. The patch below changes
the other drivers to use this filename too.
I suspect the same applies to other subsystem
Hi Andrew,
The kernel build fails, with following message
LD drivers/net/wireless/built-in.o
drivers/net/wireless/rtl8187.o: In function `rtl8225z2_rf_init':
(.opd+0x180): multiple definition of `rtl8225z2_rf_init'
drivers/net/wireless/rtl8180.o:(.opd+0x1b0): first defined here
Hi Andrew,
The kernel build fails, with following message
LD drivers/net/wireless/built-in.o
drivers/net/wireless/rtl8187.o: In function `rtl8225z2_rf_init':
(.opd+0x180): multiple definition of `rtl8225z2_rf_init'
drivers/net/wireless/rtl8180.o:(.opd+0x1b0): first defined here
> > Testing sched-cfs-v2.6.24-rc3-v24.patch on top of 2.6.24-rc3-git1
> > (ignored the two "already applied" messages coming from git1
> > commits), I get a 1.00 minimum load in top, coming from the
> > load_balance_mo thread staying in D-state. I get this on 2 different
> > computers with similar
Hi all:
* Alan Stern <[EMAIL PROTECTED]> [2007-11-19 15:27:14 -0500]:
> On Mon, 19 Nov 2007, Rudolf Marek wrote:
>
> > Hello all,
> > >>> gives coretemp_cpu_callback -> coretemp_device_remove ->
> > >>> platform_device_unregister, so coretemp seems to be what I have and you
> > >>> don't.
> > >
Hello,
> > > Ok, so it's not synchronous writes that we are doing - we're just
> > > submitting bio's tagged as WRITE_SYNC to get the I/O issued
> > > quickly. The "synchronous" nature appears to be coming from higher
> > > level locking when reclaiming inodes (on the flush lock). It
> > >
On Tue, 20 Nov 2007, Kamalesh Babulal wrote:
> Hi Andrew,
>
> The kernel build fails on AMD Opteron
>
> CC arch/x86/kernel/setup_64.o
> arch/x86/kernel/setup_64.c: In function ‘early_identify_cpu’:
> arch/x86/kernel/setup_64.c:904: warning: unused variable ‘xlvl’
>
Roland,
On Mon, 19 Nov 2007, Roland McGrath wrote:
>
> This moves the i386 vDSO sources into arch/x86/vdso/vdso32/, a
> new directory. This patch is a pure renaming, but paves the way
> for consolidating the vDSO build logic.
>
> Signed-off-by: Roland McGrath <[EMAIL PROTECTED]>
> ---
>
* [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
> Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]>
> ---
> arch/ia64/kernel/crash.c |2 +-
> drivers/base/cpu.c |2 +-
> kernel/kexec.c |4 ++--
> 3 files changed, 4 insertions(+), 4 deletions(-)
>
> Index:
* [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
> Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]>
> ---
> fs/nfs/iostat.h |8
> fs/nfs/super.c |2 +-
> 2 files changed, 5 insertions(+), 5 deletions(-)
>
> Index: linux-2.6/fs/nfs/iostat.h
>
* [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
> There is no user of local_t remaining after the cpu ops patchset. local_t
> always suffered from the problem that the operations it generated were not
> able to perform the relocation of a pointer to the target processor and the
> atomic update at
* Damien Wyart <[EMAIL PROTECTED]> wrote:
> > As usual, any sort of feedback, bugreport, fix and suggestion is
> > more than welcome!
>
> Testing sched-cfs-v2.6.24-rc3-v24.patch on top of 2.6.24-rc3-git1
> (ignored the two "already applied" messages coming from git1 commits),
> I get a 1.00
Gentlemen,
I am sorry for confusion, really do not have my day today :(.
In the last patch I mistakenly removed call to original release.
Now it should be OK.
Richard
>From 208991bcea7034202b9504c2e26c9b2edbf6e31d Mon Sep 17 00:00:00 2001
From: Richard Musil <[EMAIL PROTECTED]>
Date: Tue, 20
* [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
> Convert DMA engine to use CPU_xx operations. This also removes the use of
> local_t
> from the dmaengine.
>
> Signed-off-by: Christoph Lameter <[EMAIL PROTECTED]>
> ---
> drivers/dma/dmaengine.c | 38 ++
>
On Nov 20, 2007 7:52 AM, Herbert Xu <[EMAIL PROTECTED]> wrote:
> On Mon, Nov 19, 2007 at 10:47:59PM -0800, H. Peter Anvin wrote:
> >
> > This one is definitely messy. There is absolutely no way to know what
> > gcc has miscompiled. It looks to me that both gcc 4.2 and 4.3 are
> > affected, any
> - the internal buffer interpretation as well as the corresponding
> operations are selected at run-time by hardware detection
> - different processors use different branch record formats
I still think it would be far better if you would switch this over to be table
driven. e.g. define a
* [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
> ACPI uses NR_CPUS in various loops and in some it accesses per cpu
> data of processors that are not present(!) and that will never be present.
> The pointers to per cpu data are typically not initialized for processors
> that are not present. So we
* [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
> Using cpu alloc removes the needs for the per cpu arrays in the kmem_cache
> struct.
> These could get quite big if we have to support system of up to thousands of
> cpus.
> The use of alloc_percpu means that:
>
> 1. The size of kmem_cache for
Hi,
During a hibernate cycle on my G5, while machine was powering down after
saving the image, I just had a NULL dereference in
clockevents_program_event when accessing dev->mode, dev was NULL.
Unfortunately the machine rebooted before I was able to write down more
than the fact that it was
> #define pnp_irq(dev,bar) ((dev)->res.irq_resource[(bar)].start)
> +#define pnp_irq_start(dev,bar)((dev)->res.irq_resource[(bar)].start)
> +#define pnp_irq_end(dev,bar) ((dev)->res.irq_resource[(bar)].end)
NAK as discussed earlier.
> #define pnp_irq_flags(dev,bar)
Hello Andrew,
I am including 2nd version of the patch, slightly modified according
to your comments. See inline my response:
On 20.11.2007 7:37, Andrew Morton wrote:
> On Tue, 25 Sep 2007 15:14:50 +0200 Richard MUSIL <[EMAIL PROTECTED]> wrote:
>
>> The patch follows even more below.
>
>
On Tue, 20 Nov 2007 10:51:23 +0100
Thomas Renninger <[EMAIL PROTECTED]> wrote:
> Unify the pnp macros to access resources in the pnp resource table
NAK
> port, mem, dma and irq resource macros are now all used in the same
> way. This is the basis (or makes it at least easier) for changing how
>
401 - 500 of 1146 matches
Mail list logo
