Vitaliyi wrote:
Good Day
Say i want to implement extended set of ATA commands available to
userspace for building diagnostic tools.
I need 0x40 -- read verify and 0x32 -- write long with error handling,
for example. I was trying ide driver through ioctl's, but seems it
lack of functionality and
> On Sat, 10 Mar 2007 02:31:35 -0200 Mauro Carvalho Chehab <[EMAIL PROTECTED]>
> wrote:
> From: Trent Piepho <[EMAIL PROTECTED]>
>
> When a module uses symbol_get() to increase the ref count of another
> module, there is no record what module called symbol_get(). A module
> can
> show up as havi
* Pavel Machek <[EMAIL PROTECTED]> wrote:
> > Probably tweaking the webpage doesnt help because people dont get
> > there - as the results plainly show it. Maybe some more automation
> > would be useful too, a tool that detects failed resume and tries all
> > those options that makes sense on
Paul Menage wrote:
> On 3/6/07, Pavel Emelianov <[EMAIL PROTECTED]> wrote:
>> The idea is:
>>
>> Task may be "the entity that allocates the resources" and "the
>> entity that is a resource allocated".
>>
>> When task is the first entity it may move across containers
>> (that is implemented in your
Herbert Poetzl wrote:
> On Wed, Mar 07, 2007 at 10:19:05AM +0300, Pavel Emelianov wrote:
>> Balbir Singh wrote:
>>> Pavel Emelianov wrote:
Introduce generic structures and routines for
resource accounting.
Each resource accounting container is supposed to
aggregate it, cont
Herbert Poetzl wrote:
> On Tue, Mar 06, 2007 at 02:00:36PM -0800, Andrew Morton wrote:
>> On Tue, 06 Mar 2007 17:55:29 +0300
>> Pavel Emelianov <[EMAIL PROTECTED]> wrote:
>>
>>> +struct rss_container {
>>> + struct res_counter res;
>>> + struct list_head page_list;
>>> + struct container_subs
Le dimanche 11 mars 2007 à 11:07 +1100, Con Kolivas a écrit :
> sched rsdl fix
Doesn't change a thing. Always breaks at the same place (though
depending on hardware timings? the trace is not always the same). Pretty
sure nothing happens before this failure
--
Nicolas Mailhot
signature.asc
Desc
On Sunday 11 March 2007 20:10, Nicolas Mailhot wrote:
> Le dimanche 11 mars 2007 à 11:07 +1100, Con Kolivas a écrit :
> > sched rsdl fix
>
> Doesn't change a thing. Always breaks at the same place (though
> depending on hardware timings? the trace is not always the same). Pretty
> sure nothing happ
On Sunday 11 March 2007 20:21, Con Kolivas wrote:
> On Sunday 11 March 2007 20:10, Nicolas Mailhot wrote:
> > Le dimanche 11 mars 2007 à 11:07 +1100, Con Kolivas a écrit :
> > > sched rsdl fix
> >
> > Doesn't change a thing. Always breaks at the same place (though
> > depending on hardware timings?
[Sam Ravnborg - Sat, Mar 10, 2007 at 11:45:34PM +0100]
| On Sat, Mar 10, 2007 at 10:34:41PM +0100, Jan Engelhardt wrote:
| >
| > On Mar 10 2007 22:27, Sam Ravnborg wrote:
| > >On Sat, Mar 10, 2007 at 07:23:41PM +0100, Jan Engelhardt wrote:
| > >>
| > >> Whether the 'working config file path' shou
On Sat, 2007-03-10 at 16:42 -0800, Jeremy Fitzhardinge wrote:
> Thomas Gleixner wrote:
> > It's simply enforced in NO_HZ, HIGHRES mode as we operate in absolute
> > time, which is read back from the clocksource, even if we use a relative
> > value for real hardware clock event devices to program th
Balbir Singh wrote:
> Hi, Pavel,
>
> Please find my patch to add LRU behaviour to your latest RSS controller.
Thanks for participation and additional testing :)
I'll include this into next generation of patches.
> Balbir Singh
> Linux Technology Center
> IBM, ISTL
>
>
> ---
> On Fri, 9 Mar 2007 09:40:40 +0800 Joe Jin <[EMAIL PROTECTED]> wrote:
> > What's the error you're trying to fix? scsi_dispatch_cmd() is only
> > called from scsi_request_fn() which already has an equivalent of this
> > check in it just prior to calling dispatch.
>
> Yeah, I have saw the cheking
Hi,
The following three patches make swsusp use its own data structures for memory
management instead of special page flags. Thus the page flags used so far by
swsusp (PG_nosave, PG_nosave_free) can be used for other purposes and I believe
there are some urgend needs of them. :-)
Last week I sen
From: Rafael J. Wysocki <[EMAIL PROTECTED]>
Replace direct invocations of SetPageNosave(), SetPageNosaveFree() etc. with
calls to inline functions that can be changed in subsequent patches without
modifying the code calling them.
Signed-off-by: Rafael J. Wysocki <[EMAIL PROTECTED]>
---
include/l
From: Rafael J. Wysocki <[EMAIL PROTECTED]>
Remove the two page flags that were previously used by swsusp and are no longer
needed.
Signed-off-by: Rafael J. Wysocki <[EMAIL PROTECTED]>
---
include/linux/page-flags.h | 12
1 file changed, 12 deletions(-)
Index: linux-2.6.21-rc3/in
From: Rafael J. Wysocki <[EMAIL PROTECTED]>
Make swsusp use memory bitmaps instead of page flags for marking 'nosave' and
free pages. This allows us to 'recycle' two page flags that can be used for
other
purposes. Also, the memory needed to store the bitmaps is allocated when
necessary (ie. bef
Hi all,
as pointed out by Robert P. J. Day, here is a patch to remove unused header
files from Eicon/Dialogic ISDN driver.
Signed-off-by: Armin Schindler <[EMAIL PROTECTED]>
---
diff -Nur linux-2.6.20.1.orig/drivers/isdn/hardware/eicon/dbgioctl.h
linux-2.6.20.1/drivers/isdn/hardware/eicon/dbg
On Sun, 2007-03-11 at 11:17 +0100, Rafael J. Wysocki wrote:
> Hi,
>
> The following three patches make swsusp use its own data structures for memory
> management instead of special page flags. Thus the page flags used so far by
> swsusp (PG_nosave, PG_nosave_free) can be used for other purposes a
"Michael S. Tsirkin" <[EMAIL PROTECTED]> writes:
>> The only case I can see which might trigger this is if we saved
>> pci-X state and then didn't restore it because we could not find
>> the capability on restore.
>
> Hmm. pci_save_pcix_state/pci_restore_pcix_state seem to only handle
> regular de
Security fixes since 2.6.16.43:
- CVE-2007-0005: Fix buffer overflow in Omnikey CardMan 4040 driver
- CVE-2007-1000: [IPV6]: Handle np->opt being NULL in ipv6_getsockopt_sticky().
Location:
ftp://ftp.kernel.org/pub/linux/kernel/people/bunk/linux-2.6.16.y/testing/
git tree:
git://git.kernel.org/p
On Fri, 2007-03-09 at 10:15 +0200, Pekka J Enberg wrote:
> > + again:
> > + restart_addr = zap_page_range(vma, start_addr, end_addr - start_addr,
> > + details);
> > +
> > + need_break = need_resched() || need_lockbreak(details->i_mmap_lock);
> > + if (need_br
From: Pekka Enberg <[EMAIL PROTECTED]>
This adds special handling for revoked memory mappings. We want to
raise SIGBUS when accessing revoked mappings and return ENODEV when
trying to remap with mmap(2).
Acked-by: Alan Cox <[EMAIL PROTECTED]>
Signed-off-by: Pekka Enberg <[EMAIL PROTECTED]>
---
From: Pekka Enberg <[EMAIL PROTECTED]>
The revokeat(2) and frevoke(2) system calls invalidate open file
descriptors and shared mappings of an inode. After an successful
revocation, operations on file descriptors fail with the EBADF or
ENXIO error code for regular and device files,
respectively. At
From: Pekka Enberg <[EMAIL PROTECTED]>
Add revoke support to ext2 and ext3 by wiring f_ops->revoke with
generic_file_revoke.
Signed-off-by: Pekka Enberg <[EMAIL PROTECTED]>
---
fs/ext2/file.c |1 +
fs/ext3/file.c |1 +
2 files changed, 2 insertions(+)
Index: uml-2.6/fs/ext2/file.c
=
From: Pekka Enberg <[EMAIL PROTECTED]>
This documents revoke file operation in Documentation/filesystems/vfs.txt.
Acked-by: Alan Cox <[EMAIL PROTECTED]>
Signed-off-by: Pekka Enberg <[EMAIL PROTECTED]>
---
Documentation/filesystems/vfs.txt |5 +
1 file changed, 5 insertions(+)
Index: uml
From: Pekka Enberg <[EMAIL PROTECTED]>
Make revokeat and frevoke system calls available to user-space on i386.
Acked-by: Alan Cox <[EMAIL PROTECTED]>
Signed-off-by: Pekka Enberg <[EMAIL PROTECTED]>
---
arch/i386/kernel/syscall_table.S |3 +++
include/asm-i386/unistd.h|4 +++-
2 f
> Quoting Eric W. Biederman <[EMAIL PROTECTED]>:
> Subject: Re: SATA resume slowness, e1000 MSI warning
>
> "Michael S. Tsirkin" <[EMAIL PROTECTED]> writes:
>
> >> The only case I can see which might trigger this is if we saved
> >> pci-X state and then didn't restore it because we could not find
On Sat, 10 Mar 2007, Andrew Morton wrote:
> > On Sat, 10 Mar 2007 17:27:44 -0500 (EST) "Robert P. J. Day" <[EMAIL
> > PROTECTED]> wrote:
> >
> > Delete apparently unused header file
> > sound/pci/cs46xx/imgs/cwcemb80.h.
> >
>
> That patch series was rather a mess
>
> - Multiple patches with the
Hi Con,
On Sun, 2007-03-11 at 14:57 +1100, Con Kolivas wrote:
> What follows this email is a patch series for the latest version of the RSDL
> cpu scheduler (ie v0.29). I have addressed all bugs that I am able to
> reproduce in this version so if some people would be kind enough to test if
> th
On Sunday 11 March 2007 22:39, Mike Galbraith wrote:
> Hi Con,
>
> On Sun, 2007-03-11 at 14:57 +1100, Con Kolivas wrote:
> > What follows this email is a patch series for the latest version of the
> > RSDL cpu scheduler (ie v0.29). I have addressed all bugs that I am able
> > to reproduce in this v
On 03/10, Davide Libenzi wrote:
>
> +static void signalfd_put_sighand(struct signalfd_ctx *ctx,
> + struct sighand_struct *sighand,
> + unsigned long *flags)
> +{
> + unlock_task_sighand(ctx->tsk, flags);
> +}
Note that signalfd_put_sig
On Sun, 2007-03-11 at 22:48 +1100, Con Kolivas wrote:
>
> Thanks for the report. I'm assuming you're describing a single hyperthread P4
> here in SMP mode so 2 logical cores. Can you elaborate on whether there is
> any difference as to which cpu things are bound to as well? Can you also see
> w
* Mike Galbraith <[EMAIL PROTECTED]> wrote:
> > Full patch for 2.6.21-rc3-mm2:
> > http://ck.kolivas.org/patches/staircase-deadline/2.6.21-rc3-mm2-rsdl-0.29.patch
>
> I'm seeing a cpu distribution problem running this on my P4 box.
> With 2.6.21-rc3, X/Gforce maintain their ~50% cpu (remain sm
On Sun, 2007-03-11 at 13:10 +0100, Ingo Molnar wrote:
> * Mike Galbraith <[EMAIL PROTECTED]> wrote:
>
> > > Full patch for 2.6.21-rc3-mm2:
> > > http://ck.kolivas.org/patches/staircase-deadline/2.6.21-rc3-mm2-rsdl-0.29.patch
> >
> > I'm seeing a cpu distribution problem running this on my P4 box
Hello,
> It seems like IRQ is not getting through. The first IRQ
> driven command is failing for you.
H
> Extract is :
> ata7: PATA max UDMA/100 cmd 0x00019c00 ctl 0x00019882 bmdma
> 0x00019400 irq 16
> ata8: PATA max UDMA/100 cmd 0x00019800 ctl 0x00
> I believe you should be able to do this by sending ATA pass-through SCSI
> commands into the device using SG_IO, without any kernel changes. It's
> really the mechanism that's meant for this..
It should work, but Mark Lord reported some problems with READ_LONG on
PIIX/ICH intel chipsets. I don
Dmitriy Monakhov <[EMAIL PROTECTED]> writes:
> Greg Kroah-Hartman <[EMAIL PROTECTED]> writes:
>
>> From: James Simmons <[EMAIL PROTECTED]>
>>
>> When a device fails to register the class symlinks where not cleaned up.
>> This left a symlink in the /sys/class/"device"/ directory that pointed
>> to
|> See:
|>
http://webcvs.freedesktop.org/mesa/Mesa/src/mesa/drivers/dri/r200/r200_ioctl.c?revision=1.37&view=markup
OK.
Mesa is in git, now, but that still applies. The gitweb url is:
http://gitweb.freedesktop.org/?p=mesa/mesa.git
and for the version of the above file in the master branch:
h
On Sunday 11 March 2007 23:38, James Cloos wrote:
> |> See:
> |> http://webcvs.freedesktop.org/mesa/Mesa/src/mesa/drivers/dri/r200/r200_i
> |>octl.c?revision=1.37&view=markup
>
> OK.
>
> Mesa is in git, now, but that still applies. The gitweb url is:
>
> http://gitweb.freedesktop.org/?p=mesa/mesa.
Hi,
I have MPC 8548 Linux 2.6.x based firewall which will
mostly do packet processing for 80% time.
So obviously most of the time it will RX and TX
packets through gianfar ethernet driver.
I want to lock my interrupt handler of this driver in
the L1 cache.
1. Is there any kernel API for locking
Hi,
On Sunday 11 March 2007, Vitaliyi wrote:
> Good Day
>
> Say i want to implement extended set of ATA commands available to
> userspace for building diagnostic tools.
> I need 0x40 -- read verify and 0x32 -- write long with error handling,
Mark Lord is working on READ/WRITE_LONG support for l
ACK... Looks good...
-- james s
Linas Vepstas wrote:
Bino, James,
Please review, sign-off and forward upstream.
--linas
If a PCI error is detected that cannot be recovered from, there
will be a double call of lpfc_pci_remove_one(), with the second call
resulting in a null-pointer dereferen
Hi, list!
I have a question about coding style in linux kernel. In
Documention/CodingStyle, it is said that "Linux style for comments is
the C89 "/* ... */" style. Don't use C99-style "// ..." comments."
_But_ I see a lot of '//' style comments in current kernel code.
Which is wrong? The documen
On Sun, 2007-03-11 at 22:15 +0800, Cong WANG wrote:
[...]
> Another question is about NULL. AFAIK, in user space, using NULL is
> better than directly using 0 in C. In kernel, I know it used its own
> NULL, which may be defined as ((void*)0),
Userspace has the usually same definition.
>
On Sun, Mar 11, 2007 at 12:08:16PM +0300, Pavel Emelianov wrote:
> Herbert Poetzl wrote:
>> On Tue, Mar 06, 2007 at 02:00:36PM -0800, Andrew Morton wrote:
>>> On Tue, 06 Mar 2007 17:55:29 +0300
>>> Pavel Emelianov <[EMAIL PROTECTED]> wrote:
>>>
+struct rss_container {
+ struct res_counte
On Sunday 11 March 2007, Mike Galbraith wrote:
>Hi Con,
>
>On Sun, 2007-03-11 at 14:57 +1100, Con Kolivas wrote:
>> What follows this email is a patch series for the latest version of
>> the RSDL cpu scheduler (ie v0.29). I have addressed all bugs that I am
>> able to reproduce in this version so i
Herbert Poetzl wrote:
> On Sun, Mar 11, 2007 at 12:08:16PM +0300, Pavel Emelianov wrote:
>> Herbert Poetzl wrote:
>>> On Tue, Mar 06, 2007 at 02:00:36PM -0800, Andrew Morton wrote:
On Tue, 06 Mar 2007 17:55:29 +0300
Pavel Emelianov <[EMAIL PROTECTED]> wrote:
> +struct rss_contain
Davide,
On Sat, 2007-03-10 at 18:22 -0800, Davide Libenzi wrote:
Some remarks:
> +
> +asmlinkage long sys_timerfd(int ufd, int clockid, int tmrtype,
> + const struct timespec __user *utmr)
> +{
> + int error;
> + struct timerfd_ctx *ctx;
> + struct file *file;
Cong WANG wrote:
Hi, list!
I have a question about coding style in linux kernel. In
Documention/CodingStyle, it is said that "Linux style for comments is
the C89 "/* ... */" style. Don't use C99-style "// ..." comments."
_But_ I see a lot of '//' style comments in current kernel code.
Which is
PAGE_MASK is an unsigned long, so using it to mask physical addresses on
i386 (which are 64-bit wide) leads to truncation. This can result in
page->private of unrelated memory pages being modified, with disasterous
results.
Fix by not using PAGE_MASK for physical addresses; instead calculate
the
KVM shadow page tables are always in pae mode, regardless of the guest
setting. This means that a guest pde (mapping 4MB of memory) is mapped
to two shadow pdes (mapping 2MB each).
When the guest writes to a pte or pde, we intercept the write and emulate it.
We also remove any shadowed mappings c
This patchset contains fixes I plan to submit pre 2.6.21: a fix for
large memory 32-bit hosts, and a fix for non-pae 32-bit guests.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.or
* Avi Kivity <[EMAIL PROTECTED]> wrote:
> KVM shadow page tables are always in pae mode, regardless of the guest
> setting. This means that a guest pde (mapping 4MB of memory) is
> mapped to two shadow pdes (mapping 2MB each).
>
> When the guest writes to a pte or pde, we intercept the write
* Avi Kivity <[EMAIL PROTECTED]> wrote:
> PAGE_MASK is an unsigned long, so using it to mask physical addresses
> on i386 (which are 64-bit wide) leads to truncation. This can result
> in page->private of unrelated memory pages being modified, with
> disasterous results.
>
> Fix by not using
Subject: [patch] KVM: always reload segment selectors
From: Ingo Molnar <[EMAIL PROTECTED]>
failed VM entry on VMX might still change %fs or %gs, thus make sure
that KVM always reloads the segment selectors. This is crutial on both
x86 and x86_64: x86 has __KERNEL_PDA in %fs on which things like
Ingo Molnar wrote:
Subject: [patch] KVM: always reload segment selectors
From: Ingo Molnar <[EMAIL PROTECTED]>
failed VM entry on VMX might still change %fs or %gs, thus make sure
that KVM always reloads the segment selectors. This is crutial on both
x86 and x86_64: x86 has __KERNEL_PDA in %fs
This patchset updates the kvm userspace interface to what I hope will
be the long-term stable interface. Provisions are included for extending
the interface later. The patches address performance and cleanliness
concerns.
One patch is missing -- I'd like the string pio transfers not to include
g
This allows userspace to ignore the io.rep field. No a big deal, but
friendly.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/svm.c |1 +
drivers/kvm/vmx.c |1 +
2 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/drivers/kvm/svm.c b/drivers/kvm/svm.c
index b176
KVM used to handle cpuid by letting userspace decide what values to
return to the guest. We now handle cpuid completely in the kernel. We
still let userspace decide which values the guest will see by having
userspace set up the value table beforehand (this is necessary to allow
management softwar
Instead of passing a 'struct kvm_run' back and forth between the kernel and
userspace, allocate a page and allow the user to mmap() it. This reduces
needless copying and makes the interface expandable by providing lots of
free space.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/
Older userspace didn't care, but newer userspace (with the cpuid changes)
does.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/svm.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/drivers/kvm/svm.c b/drivers/kvm/svm.c
index 0311665..2396ada 100644
--- a/
The recent changes have left the ioctl numbers in complete disarray.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
include/linux/kvm.h | 34 +-
1 files changed, 17 insertions(+), 17 deletions(-)
diff --git a/include/linux/kvm.h b/include/linux/kvm.h
index d8
That ioctl does not transfer any data, so it should be an _IO rather than an
_IOW.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
include/linux/kvm.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/include/linux/kvm.h b/include/linux/kvm.h
index c6dd4a7..d89189a 10064
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/kvm_main.c |6 ++
include/linux/kvm.h|5 +
2 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/drivers/kvm/kvm_main.c b/drivers/kvm/kvm_main.c
index 747966e..376538c 100644
--- a/drivers/kvm/kvm_main.c
++
This allows us to store offsets in the kernel/user kvm_run area, and be
sure that userspace has them mapped. As offsets can be outside the
kvm_run struct, userspace has no way of knowing how much to mmap.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/kvm_main.c |8 +++-
i
Allow a special signal mask to be used while executing in guest mode. This
allows signals to be used to interrupt a vcpu without requiring signal
delivery to a userspace handler, which is quite expensive. Userspace still
receives -EINTR and can get the signal via sigwait().
Signed-off-by: Avi Ki
We no longer emulate single instructions in userspace. Instead, we service
mmio or pio requests.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/kvm_main.c |5 -
include/linux/kvm.h|3 +--
2 files changed, 1 insertions(+), 7 deletions(-)
diff --git a/drivers/kvm/kv
This is redundant, as we also return -EINTR from the ioctl, but it
allows us to examine the exit_reason field on resume without seeing
old data.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/svm.c |2 ++
drivers/kvm/vmx.c |2 ++
include/linux/kvm.h |3 ++-
3 files
This is useful for paravirtualized graphics devices, for example.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/kvm_main.c | 18 +-
include/linux/kvm.h| 10 +-
2 files changed, 26 insertions(+), 2 deletions(-)
diff --git a/drivers/kvm/kvm_main.c b/
Currently when passing the a PIO emulation request to userspace, we
rely on userspace updating %rax (on 'in' instructions) and %rsi/%rdi/%rcx
(on string instructions). This (a) requires two extra ioctls for getting
and setting the registers and (b) is unfriendly to non-x86 archs, when
they get kvm
Some ioctls ignore their arguments. By requiring them to be zero now,
we allow a nonzero value to have some special meaning in the future.
Signed-off-by: Avi Kivity <[EMAIL PROTECTED]>
---
drivers/kvm/kvm_main.c |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/dri
Currently, userspace is told about the nature of the last exit from the
guest using two fields, exit_type and exit_reason, where exit_type has
just two enumerations (and no need for more). So fold exit_type into
exit_reason, reducing the complexity of determining what really happened.
Signed-off-
> -procfs-fix-race-between-proc_readdir-and-remove_proc_entry.patch
> +fix-race-between-proc_get_inode-and-remove_proc_entry.patch
>
> Updated. Looks sane.
Why have you dropped the first patch? Resending slightly fixed version
of it.
[PATCH -mm] Fix race between proc_readdir and remove_proc_en
Andrew Morton wrote:
> On Tue, 06 Mar 2007 17:55:29 +0300
> Pavel Emelianov <[EMAIL PROTECTED]> wrote:
>
>
>>+struct rss_container {
>>+ struct res_counter res;
>>+ struct list_head page_list;
>>+ struct container_subsys_state css;
>>+};
>>+
>>+struct page_container {
>>+ struct p
> On Sun, 11 Mar 2007 15:26:41 +0300 Kirill Korotaev <[EMAIL PROTECTED]> wrote:
> Andrew Morton wrote:
> > On Tue, 06 Mar 2007 17:55:29 +0300
> > Pavel Emelianov <[EMAIL PROTECTED]> wrote:
> >
> >
> >>+struct rss_container {
> >>+ struct res_counter res;
> >>+ struct list_head page_list;
> >>
On Fri, 2007-03-09 at 09:40 +0800, Joe Jin wrote:
> > What's the error you're trying to fix? scsi_dispatch_cmd() is only
> > called from scsi_request_fn() which already has an equivalent of this
> > check in it just prior to calling dispatch.
>
> Yeah, I have saw the cheking at scsi_request_fn(),
On 3/11/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
> On Sun, 11 Mar 2007 15:26:41 +0300 Kirill Korotaev <[EMAIL PROTECTED]> wrote:
> Andrew Morton wrote:
> > On Tue, 06 Mar 2007 17:55:29 +0300
> > Pavel Emelianov <[EMAIL PROTECTED]> wrote:
> >
> >
> >>+struct rss_container {
> >>+ struct res_
On Fri, 09 Mar 2007 20:24:42 PST, Randy Dunlap said:
> On Fri, 09 Mar 2007 23:03:05 -0500 [EMAIL PROTECTED] wrote:
> > -/* GCC is awesome. */
> > +/* GCC leaves me speechless. */
>
> "awesome" can mean "inspiring awe or admiration or wonder" (amazing)
> or it can mean "awful" (as in terrifying).
On Sat, 10 Mar 2007, Nicholas Miell wrote:
> >
> > UNIX has pid's for "process" handles, and "file descriptors" for just
> > about everything else.
>
> And I imagine that somebody will come up with way of getting a fd for a
> process sooner or later.
Well, /proc// is about as close as you ge
"Michael S. Tsirkin" <[EMAIL PROTECTED]> writes:
>> Quoting Eric W. Biederman <[EMAIL PROTECTED]>:
>> Subject: Re: SATA resume slowness, e1000 MSI warning
>>
>> "Michael S. Tsirkin" <[EMAIL PROTECTED]> writes:
>>
>> >> The only case I can see which might trigger this is if we saved
>> >> pci-X s
On Saturday, 3 March 2007 18:32, Oleg Nesterov wrote:
> On 03/02, Paul E. McKenney wrote:
> >
> > On Sat, Mar 03, 2007 at 02:33:37AM +0300, Oleg Nesterov wrote:
> > > On 03/02, Paul E. McKenney wrote:
> > > >
> > > > One way to embed try_to_freeze() into kthread_should_stop() might be
> > > > as fo
Paul,
do I understand correctly that the *only* difference between the working
setup is that you applied (by hand) the libata patch that Jeff sent out?
So plain 2.6.21-rc2 works fine, but with the patch applied, you get no
interrupts on the DVD drive?
On Sun, 11 Mar 2007, Paul Rolland wrote:
On Sun, 11 Mar 2007, Andi Kleen wrote:
> This and i386 version are ok to me, although it might be better to just
> finish __GFP_ZERO support to do this.
This would not work for pgds on i386 and x86_64
GFP_ZERO support the way I have done it in the past would mean another set
of buddy lists in t
> Quoting Roland Dreier <[EMAIL PROTECTED]>:
> Subject: Re: IPoIB caused a kernel: BUG: soft lockup detected on CPU#0!
>
> >Feb 27 17:47:52 sw169 kernel: []
> >_spin_lock_irqsave+0x15/0x24
> >Feb 27 17:47:52 sw169 kernel: []
> >:ib_ipoib:ipoib_neigh_destructor+0xc2/0x139
>
> It looks like thi
> Quoting Michael S. Tsirkin <[EMAIL PROTECTED]>:
> Subject: Re: lockdep question (was Re: IPoIB caused a kernel: BUG: soft
> lockup detected on CPU#0!)
>
>
> After adding some printks, I started getting these:
>
> [ 597.036720] BUG: MAX_STACK_TRACE_ENTRIES too low!
> [ 597.041546] turning of
On Sun, 2007-03-11 at 15:50 +0200, Michael S. Tsirkin wrote:
> > Quoting Roland Dreier <[EMAIL PROTECTED]>:
> > Subject: Re: IPoIB caused a kernel: BUG: soft lockup detected on CPU#0!
> >
> > >Feb 27 17:47:52 sw169 kernel: []
> > >_spin_lock_irqsave+0x15/0x24
> > >Feb 27 17:47:52 sw169 kernel:
After adding some printks, I started getting these:
[ 597.036720] BUG: MAX_STACK_TRACE_ENTRIES too low!
[ 597.041546] turning off the locking correctness validator.
[ 597.047135] [] save_trace+0x8a/0x8f
[ 597.051751] [] mark_lock+0x65/0x3ff
[ 597.056366] [] save_trace+0x3e/0x8f
[ 597.060
Quoting Peter Zijlstra <[EMAIL PROTECTED]>:
Subject: Re: lockdep question (was Re: IPoIB caused a kernel: BUG: softlockup
detected on CPU#0!)
> On Sun, 2007-03-11 at 15:50 +0200, Michael S. Tsirkin wrote:
> > > Quoting Roland Dreier <[EMAIL PROTECTED]>:
> > > Subject: Re: IPoIB caused a kernel: B
Differences from version 4:
Updated in-code comments. Largely rewritten changelog.
Lockdep please. --akpm
->read_proc, ->write_proc aren't special, Extend protection to
most methods for regular /proc files. Mentioned by viro.
Differences from version 3:
Use c
> Rumor has it that some pci devices can't tolerate < 32bit accesses.
> Although I have never met one.
hopefully not bridge devices?
> The two factors together suggest that
> for generic code it probably makes sense to operate on 32bit
> quantities, and just to ignore the read-only portion.
The
Al Boldi wrote:
> BTW, another way to show these hickups would be through some kind of a
> cpu/proc timing-tracer. Do we have something like that?
Here is something like a tracer.
Original idea by Chris Friesen, thanks, from this post:
http://marc.theaimsgroup.com/?l=linux-kernel&m=1173310030293
Suspend to disk doesn't work on my laptop.
The suspend seems to hang while enabling the non-boot cpus again.
with platform = "test" and state = "disk" i get this:
"
[cut]
acpi device:02: freeze
video video:00: freeze
acpi device:01: freeze
acpi PNP0C02:00: freeze
pci_root PNP0A08:00: freeze
butt
On Sun, 11 Mar 2007, Oleg Nesterov wrote:
> On 03/10, Davide Libenzi wrote:
> >
> > +static void signalfd_put_sighand(struct signalfd_ctx *ctx,
> > +struct sighand_struct *sighand,
> > +unsigned long *flags)
> > +{
> > + unlock_task_sighand
On Sunday, 11 March 2007 19:08, Thomas Meyer wrote:
> Suspend to disk doesn't work on my laptop.
>
> The suspend seems to hang while enabling the non-boot cpus again.
>
> with platform = "test" and state = "disk" i get this:
> "
> [cut]
> acpi device:02: freeze
> video video:00: freeze
> acpi dev
Hi all,
I'm planning to remove the i8xx_tco watchdog driver
(since we now have the iTCO_wdt driver that has a broader scope).
If no-one objects I will sent the below patch to Linus for inclusion.
(it adds the driver to the feature-removal-schedule list and defaults
CONFIG_I8XX_TCO to n).
Thanks,
On Sun, 11 Mar 2007, Thomas Gleixner wrote:
> Davide,
>
> On Sat, 2007-03-10 at 18:22 -0800, Davide Libenzi wrote:
>
> Some remarks:
>
> > +
> > +asmlinkage long sys_timerfd(int ufd, int clockid, int tmrtype,
> > + const struct timespec __user *utmr)
> > +{
> > + int err
"Michael S. Tsirkin" <[EMAIL PROTECTED]> writes:
>> Rumor has it that some pci devices can't tolerate < 32bit accesses.
>> Although I have never met one.
>
> hopefully not bridge devices?
>
>> The two factors together suggest that
>> for generic code it probably makes sense to operate on 32bit
>>
Rafael J. Wysocki schrieb:
Could you please put some printk()s in kernel/cpu.c:_cpu_up() to see where
it gets stuck? I bet one of the notifiers goes to sleep (cpufreq, maybe).
Here we go (ok. i forgot __FUNCTION__ ...):
Mar 11 19:31:33 [kernel] ac ACPI0003:00: freeze
Mar 11 19:31:33 [kerne
Herbert Poetzl <[EMAIL PROTECTED]> writes:
>
> Linux-VServer does the accounting with atomic counters,
> so that works quite fine, just do the checks at the
> beginning of whatever resource allocation and the
> accounting once the resource is acquired ...
Atomic operations versus locks is only a
1 - 100 of 237 matches
Mail list logo
