Work in progress, not for inclusion.
This patch modified the RCU priority booster to explicitly sleep when
there are no RCU readers in need of priority boosting. This should be
a power-consumption improvement over the one-second polling cycle in
the underlying RCU priority-boosting patch.
Signed
Work in progress, not for inclusion. Still uses xtime because this
patch is still against 2.6.22.
This patch modifies rcutorture to also torture RCU priority boosting.
The torturing involves forcing RCU read-side critical sections (already
performed as part of the torturing of RCU) to run for ext
Work in progress, not for inclusion.
RCU priority boosting is needed when running a workload that might include
CPU-bound user tasks running at realtime priorities with preemptible RCU.
In this situation, RCU priority boosting is needed to avoid OOM.
Please note that because Classic RCU does not
On 9/10/07, Srivatsa Vaddagiri <[EMAIL PROTECTED]> wrote:
>
> Unless folks have strong objection to it, I prefer "cptctlr", the way it is.
>
By definition any container (about to be renamed control group)
subsystem is some kind of "controller" so that bit seems a bit
redundant.
Any reason not to
Work in progress, not for inclusion.
This patch allows preemptible RCU to tolerate CPU-hotplug operations.
It accomplishes this by maintaining a local copy of a map of online
CPUs, which it accesses under its own lock.
Signed-off-by: Paul E. McKenney <[EMAIL PROTECTED]>
---
include/linux/rcucl
Work in progress, not for inclusion.
The combination of CPU hotplug and PREEMPT_RCU has resulted in deadlocks
due to the migration-based implementation of synchronize_sched() in -rt.
This experimental patch maps synchronize_sched() back onto Classic RCU,
eliminating the migration, thus hopefully a
Work in progress, not for inclusion.
This patch implements a new version of RCU which allows its read-side
critical sections to be preempted. It uses a set of counter pairs
to keep track of the read-side critical sections and flips them
when all tasks exit read-side critical section. The details
o
Work in progress, not for inclusion.
Fix rcu_barrier() to work properly in preemptive kernel environment.
Also, the ordering of callback must be preserved while moving
callbacks to another CPU during CPU hotplug.
Signed-off-by: Dipankar Sarma <[EMAIL PROTECTED]>
Signed-off-by: Paul E. McKenney <[
Work in progress, not for inclusion.
This patch re-organizes the RCU code to enable multiple implementations
of RCU. Users of RCU continues to include rcupdate.h and the
RCU interfaces remain the same. This is in preparation for
subsequently merging the preemptible RCU implementation.
Signed-off-
Work in progress, still not for inclusion. But code now complete!
This is a respin of the following prior posting:
http://lkml.org/lkml/2007/9/5/268
This release adds an additional patch that adds fixes to comments and RCU
documentation, along with one macro being renamed. The rcutorture patch
On Mon, 10 Sep 2007 18:49:26 +0100 Andy Whitcroft <[EMAIL PROTECTED]> wrote:
> I have a couple of old NUMA-Q systems which are unable to read their
> boot disks with 2.6.23-rc4-mm1. The disks appear to be recognised and
> even the partition tables read correctly, and then they go pop:
>
> qla1
On Monday 10 September 2007 14:08:45 Laurent Vivier wrote:
> Avi Kivity wrote:
> > Ingo Molnar wrote:
> >> * Laurent Vivier <[EMAIL PROTECTED]> wrote:
> >>> Ingo, please, could you have a look to these patches ?
> >>>
> >>> The aim of these four patches is to introduce Virtual Machine time
> >>> ac
On Mon, 10 Sep 2007, Bruce Allen wrote:
> Dear LKML,
>
> Apologies in advance for potential mis-use of LKML, but I don't know where
> else to ask.
>
> An ongoing study on datasets of several Petabytes have shown that there
> can be 'silent data corruption' at rates much larger than one might
> na
J. Bruce Fields wrote:
On Fri, Sep 07, 2007 at 03:32:32PM +0530, Kamalesh Babulal wrote:
Sep 7 11:42:49 p55lp2 kernel: kernel BUG at fs/nfs/nfs4xdr.c:945!
That's the first line of encode_lookup:
static int encode_lookup(struct xdr_stream *xdr, const struct qstr
*name)
On Mon, Sep 10, 2007 at 01:20:38PM +0100, Maciej W. Rozycki wrote:
> Remove typedefs, volatiles and convert kmalloc()/memset() pairs to
> kcalloc(). Also reformat the surrounding clutter.
>
> Signed-off-by: Maciej W. Rozycki <[EMAIL PROTECTED]>
> ---
> Per your request, Andrew, a while ago. I
On Mon, 10 Sep 2007 18:44:54 +0100 Alan Cox <[EMAIL PROTECTED]> wrote:
> > A single kernel release seems sufficient. It gives the maintainers of such
> > code time to hear about the breakage and time to fix it.
>
> Users don't report warnings generally. They won't even see modprobe
> warnings or
I have a couple of old NUMA-Q systems which are unable to read their
boot disks with 2.6.23-rc4-mm1. The disks appear to be recognised and
even the partition tables read correctly, and then they go pop:
qla1280: QLA1040 found on PCI bus 0, dev 10
Clocksource tsc unstable (delta = 99922590 ns)
On Sep 10 2007 10:22, Andrew Morton wrote:
>> Unless folks have strong objection to it, I prefer "cptctlr", the way it is.
>
>Kernel code is write-rarely, read-often.
I think you mean __read_mostly. :-)
Jan
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On Sep 10 2007 22:58, Srivatsa Vaddagiri wrote:
>On Mon, Sep 10, 2007 at 10:53:34PM +0530, Srivatsa Vaddagiri wrote:
>> > cpuctl, cpuctrl, cpu_controller?
>>
>> *shrug* .. I used "cpuctlr" to mean "CPU Controller". Any other short names
>> would do. From your list, cpuctl or cpuctrl both qualifie
Am seeing the following compile error on all of my powerpc platforms:
CC kernel/sched.o
kernel/sched.c: In function `cpu_to_phys_group':
kernel/sched.c:5937: error: `per_cpu__cpu_sibling_map' undeclared (first use
in this function)
kernel/sched.c:5937: error: (Each undeclared identif
On Mon, Sep 10, 2007 at 02:05:47PM +0200, Johannes Berg wrote:
> To implement the multicast list callback in mac80211 we need to
> do partial list iteration. Since I want to convert the interface
> list to an RCU list, I need a new list walking primitive:
> list_for_each_entry_continue_rcu().
>
>
> A single kernel release seems sufficient. It gives the maintainers of such
> code time to hear about the breakage and time to fix it.
Users don't report warnings generally. They won't even see modprobe
warnings or anything in dmesg. Short of using their sound card to scream
"Next release you ar
On Mon, Sep 10, 2007 at 10:22:59AM -0700, Andrew Morton wrote:
> objection ;) "cpuctlr" isn't memorable. Kernel code is write-rarely,
> read-often. "cpu_controller", please. The extra typing is worth it ;)
Ok! Here's the modified patch (against 2.6.23-rc4-mm1).
Signed-off-by : Srivatsa Vaddag
On Mon, Sep 10, 2007 at 03:37:48AM +1000, Paul Mackerras wrote:
> Keshavamurthy, Anil S writes:
>
> > Subject: [RFC][Intel-IOMMU] Fix for IOMMU early crash
> >
> > Populating pci_bus->sysdata way early in the pci discovery phase
> > sets NON-NULL value to pci_dev->sysdata which breaks the assumpt
On Mon, 10 Sep 2007 13:43:58 +0100 Al Viro <[EMAIL PROTECTED]> wrote:
> On Mon, Sep 10, 2007 at 02:23:24AM -0700, Andrew Morton wrote:
> > > And I think almost everyone disagrees with you. We just carry too much
> > > crap around because of your subborness in this issue, and it gets really
> > >
On Mon, 10 Sep 2007 22:53:34 +0530 Srivatsa Vaddagiri <[EMAIL PROTECTED]> wrote:
> On Mon, Sep 10, 2007 at 07:05:00PM +0200, Jan Engelhardt wrote:
> > On Sep 10 2007 22:40, Srivatsa Vaddagiri wrote:
> > >+#ifdef CONFIG_FAIR_GROUP_SCHED
> > >+SUBSYS(cpuctlr)
> > >+#endif
> >
> > cpuctl, cpuctrl, c
On Mon, Sep 10, 2007 at 10:53:34PM +0530, Srivatsa Vaddagiri wrote:
> > cpuctl, cpuctrl, cpu_controller?
>
> *shrug* .. I used "cpuctlr" to mean "CPU Controller". Any other short names
> would do. From your list, cpuctl or cpuctrl both qualifies IMO!
>
> Unless folks have strong objection to it,
On Mon, Sep 10, 2007 at 07:05:00PM +0200, Jan Engelhardt wrote:
> On Sep 10 2007 22:40, Srivatsa Vaddagiri wrote:
> >+#ifdef CONFIG_FAIR_GROUP_SCHED
> >+SUBSYS(cpuctlr)
> >+#endif
>
> cpuctl, cpuctrl, cpu_controller?
*shrug* .. I used "cpuctlr" to mean "CPU Controller". Any other short names
woul
On Sun, Sep 09, 2007 at 08:51:40PM +0300, Muli Ben-Yehuda wrote:
> On Mon, Sep 10, 2007 at 08:43:59AM -0700, Keshavamurthy, Anil S wrote:
> > On Sun, Sep 09, 2007 at 02:16:19PM +0300, Muli Ben-Yehuda wrote:
> > > On Sat, Sep 08, 2007 at 01:05:24PM -0700, Keshavamurthy, Anil S wrote:
> > >
> > > >
On Mon, 10 Sep 2007 14:39:34 BST, Alan Cox said:
> On Mon, 10 Sep 2007 16:20:42 +0300
> Sami Farin <[EMAIL PROTECTED]> wrote:
>
> > On Mon, Sep 10, 2007 at 13:59:12 +0100, Alan Cox wrote:
> > > Will RMK ([EMAIL PROTECTED]) please fix his email setup otherwise I
> > > can't send serial/tty/arm stuf
On Sep 10 2007 22:40, Srivatsa Vaddagiri wrote:
>+#ifdef CONFIG_FAIR_GROUP_SCHED
>+SUBSYS(cpuctlr)
>+#endif
cpuctl, cpuctrl, cpu_controller?
-
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.
Ingo and Andrew,
The cfs core has been enhanced since quite sometime now to
understand task-groups and provide fairness to such task-group. What was
needed is an interface for the administrator to define task-groups and
specify group "importance" in terms of its cpu share.
The patch below
Nick Piggin wrote:
>
> +void *dyn_data_replace(struct dyn_data *dd, dd_transfer_fn fn, void *new)
> +{
> + int xfer_done;
> + void *old;
> +
> + BUG_ON(!mutex_is_locked(&dd->resize_mutex));
> + old = dd->cur;
> + BUG_ON(dd->old);
> + dd->old = old;
> + synchronize_rcu();
On Monday 10 September 2007 16:09, Linus Torvalds wrote:
> On Mon, 10 Sep 2007, Denys Vlasenko wrote:
> > static inline int
> > qla2x00_wait_for_loop_ready(scsi_qla_host_t *ha)
> > {
> > int return_status = QLA_SUCCESS;
> > unsigned long loop_timeout ;
> > scsi_qla_host
On Mon, Sep 10, 2007 at 09:35:52PM +0530, pradeep singh rautela wrote:
> Hi,
>
> I am facing some problem understanding and using the kernel Kbuild
> system. I tried googling but not much of help.
>
> Thanks to a good kbuild documentation in the tree. It looks like $(LD)
> -r is not able to do wh
On Fri, Sep 07 2007, Simon Holm Thøgersen wrote:
> tir, 04 09 2007 kl. 23:06 +0200, skrev Jens Axboe:
> > On Tue, Sep 04 2007, Simon Holm Thøgersen wrote:
> > > tir, 04 09 2007 kl. 13:06 +0200, skrev Jens Axboe:
> > > > On Tue, Sep 04 2007, Micah Gruber wrote:
> > > > > This patch fixes a potential
ide-cd needs a new maintainer. I'm now at the point where I simply don't
have any old-ide systems or interest in working on old IDE bugs at all.
So if someone would care to take it over please say otherwise I'll send
Akpm a patch to mark it unmaintained
-
To unsubscribe from this list: send the l
On Mon, 10 Sep 2007 08:06:20 -0700 (PDT)
PnP driver <[EMAIL PROTECTED]> wrote:
>
> Hi,
> I am very new to linux kernel driver development. I need to develop a
> driver for calling BIOS routines like get device node. I could call it
> in i386 architecture using the PnP driver.
We u
On Sep 10 2007 21:35, pradeep singh rautela wrote:
>
>So , here is the question in short...
>
>What do i need to change and where to make sure this thing vanishes
>away and kernel compiles as usual like it always did earlier?
Perhaps post a patch that demonstrates the problem in short.
>Any poin
On Mon, 2007-09-10 at 08:18 -0700, Daniel Walker wrote:
> On Mon, 2007-09-10 at 14:35 +0200, Peter Zijlstra wrote:
>
> > > - simple_irq change (Kevin Hilman): needs more thought
> > > - RCU updates (Paul McKenney): needs proper integration
> > > - latency tracer changes (Daniel Walker): needs revi
On Mon, 10 Sep 2007 18:01:34 +0200 Laurent Vivier wrote:
> Randy Dunlap wrote:
> > On Mon, 10 Sep 2007 16:12:58 +0200 Laurent Vivier wrote:
> >
> >> [PATCH 3/4] modify account_system_time() to add cputime to cpustat->guest
> >> if we
> >> are running a VCPU. We add this cputime to cpustat->user
Hi,
I am facing some problem understanding and using the kernel Kbuild
system. I tried googling but not much of help.
Thanks to a good kbuild documentation in the tree. It looks like $(LD)
-r is not able to do what it is supposed to do. May be i am doing
something wrong?
here is a brief summary
On Mon, 10 Sep 2007 15:38:23 +0100
Denys Vlasenko <[EMAIL PROTECTED]> wrote:
> On Monday 10 September 2007 15:51, Arjan van de Ven wrote:
> > On Mon, 10 Sep 2007 11:56:29 +0100
> > Denys Vlasenko <[EMAIL PROTECTED]> wrote:
> >
> > >
> > > Well, if you insist on having it again:
> > >
> > > Wait
Randy Dunlap wrote:
> On Mon, 10 Sep 2007 16:12:58 +0200 Laurent Vivier wrote:
>
>> [PATCH 3/4] modify account_system_time() to add cputime to cpustat->guest if
>> we
>> are running a VCPU. We add this cputime to cpustat->user instead of
>> cpustat->system because this part of KVM code is in fac
[ This needs to go into 2.6.23 ]
The earlier crash dump fix on x86_64 depended on patches in -mm which
are intended for post-2.6.23. Without those, it broke the build when
it went into 2.6.23-rc5.
This patch changes the field references in ELF_CORE_COPY_REGS back to
those still used in mainline.
On Mon, 10 Sep 2007 16:12:58 +0200 Laurent Vivier wrote:
> [PATCH 3/4] modify account_system_time() to add cputime to cpustat->guest if
> we
> are running a VCPU. We add this cputime to cpustat->user instead of
> cpustat->system because this part of KVM code is in fact user code although it
> is
On Mon, Sep 10, 2007 at 10:32:45AM -0400, Bill Davidsen wrote:
> Adrian Bunk wrote:
>> On Sat, Sep 08, 2007 at 01:44:20PM -0400, Bill Davidsen wrote:
>>
>>> ...
>>> That was with 2.6.22.5 (or so), dropped back to an old kernel with
>>> sk98lin, previously had uptimes in three digit days. Up for
Yishai Hadas wrote:
Hi List,
I'm looking for any mechanism in a multi-threaded process to monitor the
health of its running threads - or by a specific monitor thread or by
any other mechanism.
It includes the following aspects:
1) Threads are running and not stuck on any lock.
If you're
On Mon, 2007-09-10 at 14:35 +0200, Peter Zijlstra wrote:
> > - simple_irq change (Kevin Hilman): needs more thought
> > - RCU updates (Paul McKenney): needs proper integration
> > - latency tracer changes (Daniel Walker): needs review
> > - PICK_OP changes (Daniel Walker): needs review
>
> This o
> From: Adrian Bunk [mailto:[EMAIL PROTECTED]
> Sent: Sunday, September 09, 2007 1:25 PM
> To: Andrew Morton; Nelson, Shannon; Williams, Dan J
> Cc: linux-kernel@vger.kernel.org
> Subject: [-mm patch] drivers/dma/ioat_dma.c: make 3 functions static
>
Thanks Adrian,
sln
>On Fri, Aug 31, 2007 at
The inode->i_flock list contains the leases, flocks and posix
locks in the specified order. However, the flocks are added in
the head of this list thus hiding the leases from F_GETLEASE
command, from time_out_leases() and other code that expects
the leases to come first.
The following example will
On Mon, 10 Sep 2007, Denys Vlasenko wrote:
>
> static inline int
> qla2x00_wait_for_loop_ready(scsi_qla_host_t *ha)
> {
> int return_status = QLA_SUCCESS;
> unsigned long loop_timeout ;
> scsi_qla_host_t *pha = to_qla_parent(ha);
>
> /* wait for 5 min at the
On 9/10/07, Adrian McMenamin <[EMAIL PROTECTED]> wrote:
> On 10/09/2007, Dmitry Torokhov <[EMAIL PROTECTED]> wrote:
> > Hi Adrian,
> >
>
> Thanks for the comments - will get on with this but
>
>
> > > + for (i = 0; i < NR_SCANCODES; i++)
> > > + kbd->keycode[i] = dc_kbd_keycode[
Hi,
I am very new to linux kernel driver development. I need to develop a
driver for calling BIOS routines like get device node. I could call it
in i386 architecture using the PnP driver.
But in x86_64 arch I couldn't see any support. Even I tried to
implement it similar to the
Rik van Riel wrote:
> Laurent Vivier wrote:
>> [PATCH 1/4] as recent CPUs introduce a third running state, after
>> "user" and
>> "system", we need a new field, "guest", in cpustat to store the time
>> used by
>> the CPU to run virtual CPU. Modify /proc/stat to display this new field.
>
> I think
Duane Griffin wrote:
> Hi Eric,
>
> On Fri, Aug 31, 2007 at 09:48:43PM -0500, Eric Sandeen wrote:
>> (resend, this one got lost? Got an acked-by from Andreas
>> last go-round)
>
> Sorry I missed this first time around. I came up with a very similar
> fix recently, following a gentoo bug report.
If the ATTR_KILL_S*ID bits are set then any mode change is only for
clearing the setuid/setgid bits. For CIFS, skip the mode change and
let the server handle it.
Signed-off-by: Jeff Layton <[EMAIL PROTECTED]>
---
fs/cifs/inode.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff
If the ATTR_KILL_S*ID bits are set then any mode change is only for
clearing the setuid/setgid bits. For NFS skip the mode change and
let the server handle it.
Signed-off-by: Jeff Layton <[EMAIL PROTECTED]>
---
fs/nfs/inode.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --g
Don't allow either function to trip the BUG() in notify_change. For
unionfs_setattr, clear ATTR_MODE if the either ATTR_KILL_S*ID is set.
unionfs_create is setting the mode explicitly already. Don't set
ATTR_KILL_S*ID. Just fix up the mode to have the same effect. Also, move
locking the i_mutex t
reiserfs_setattr can call notify_change recursively using the same
iattr struct. This could cause it to trip the BUG() in notify_change.
Fix reiserfs to clear those bits near the beginning of the function.
Signed-off-by: Jeff Layton <[EMAIL PROTECTED]>
---
fs/reiserfs/inode.c |6 +-
1 fil
Make notify_change not clear the ATTR_KILL_S*ID bits in the ia_vaid that
gets passed to the setattr inode operation. This allows the filesystems
to reinterpret whether this mode change is simply intended to clear the
setuid/setgid bits.
This means that notify_change should never be called with bot
Make sure ecryptfs doesn't trip the BUG() in notify_change. This also
allows the lower filesystem to interpret these bits in their own way.
Signed-off-by: Jeff Layton <[EMAIL PROTECTED]>
---
fs/ecryptfs/inode.c |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/fs/ecr
It's theoretically possible for a single SETATTR call to come in that
sets the mode and the uid/gid. In that case, assume the mode is
correct and don't set the ATTR_KILL_S*ID bits. Doing so would trip the
BUG() in notify_change.
Signed-off-by: Jeff Layton <[EMAIL PROTECTED]>
---
fs/nfsd/vfs.c |
When an unprivileged process attempts to modify a file that has the
setuid or setgid bits set, the VFS will attempt to clear these bits. The
VFS will set the ATTR_KILL_SUID or ATTR_KILL_SGID bits in the ia_valid
mask, and then call notify_change to clear these bits and set the mode
accordingly.
Wi
Laurent Vivier wrote:
[PATCH 1/4] as recent CPUs introduce a third running state, after "user" and
"system", we need a new field, "guest", in cpustat to store the time used by
the CPU to run virtual CPU. Modify /proc/stat to display this new field.
I think it would be good to always print out t
On 09/09/2007, J. Bruce Fields <[EMAIL PROTECTED]> wrote:
> > When accessing a directory inode from a single other client, NFSv4
> > callbacks catastrophically failed [1] on the NFS server with
> > 2.6.23-rc4 (unpatched); clients are both 2.6.22 (Ubuntu Gutsy build).
> > Seems not easy to reproduce
On Monday 10 September 2007 15:51, Arjan van de Ven wrote:
> On Mon, 10 Sep 2007 11:56:29 +0100
> Denys Vlasenko <[EMAIL PROTECTED]> wrote:
>
> >
> > Well, if you insist on having it again:
> >
> > Waiting for atomic value to be zero:
> >
> > while (atomic_read(&x))
> >
Adrian Bunk wrote:
On Sat, Sep 08, 2007 at 01:44:20PM -0400, Bill Davidsen wrote:
...
That was with 2.6.22.5 (or so), dropped back to an old kernel with sk98lin,
previously had uptimes in three digit days. Up for a week or so now.
There is a real long-term advantage of removing driver
On 10/09/2007, Dmitry Torokhov <[EMAIL PROTECTED]> wrote:
> Hi Adrian,
>
Thanks for the comments - will get on with this but
> > + for (i = 0; i < NR_SCANCODES; i++)
> > + kbd->keycode[i] = dc_kbd_keycode[i];
>
> memcpy?
>
I see that other drivers use memcpy - and will happi
Hi developers,
I am looking for your insights and attitudes towards modeling.
If you are interested and have 20 minutes, the survey is available at:
http://cruise.site.uottawa.ca/awf2/ask/models
I have contacted the Linux community because I am currently looking
for a few more responses from tho
On Monday 10 September 2007 14:38, Denys Vlasenko wrote:
> You are basically trying to educate me how to use atomic properly.
> You don't need to do it, as I am (currently) not a driver author.
>
> I am saying that people who are already using atomic_read()
> (and who unfortunately did not read yo
[PATCH 4/4] Modify KVM to update guest time accounting.
Signed-off-by: Laurent Vivier <[EMAIL PROTECTED]>
--
- [EMAIL PROTECTED] --
"Software is hard" - Donald Knuth
Index: linux-2.6/drivers/kvm/kvm.h
===
On Mon, 10 Sep 2007 02:23:24 -0700
Andrew Morton <[EMAIL PROTECTED]> wrote:
> I would like to see "everyone" explain what we lose by giving
> developers a bit of warning before we break their stuff.
here's the skinny: 99% of the external module developers won't notice
until they're gone, even wit
[PATCH 2/4] like for cpustat, introduce the "gtime" (guest time of the task) and
"cgtime" (guest time of the task children) fields for the
tasks. Modify signal_struct and task_struct. Modify /proc//stat to display
these new fields.
Signed-off-by: Laurent Vivier <[EMAIL PROTECTED]>
--
[PATCH 3/4] modify account_system_time() to add cputime to cpustat->guest if we
are running a VCPU. We add this cputime to cpustat->user instead of
cpustat->system because this part of KVM code is in fact user code although it
is executed in the kernel. We duplicate VCPU time between guest and use
This new version remove conditional compilation on GUEST_ACCOUNTING.
--
The aim of these four patches is to introduce Virtual Machine time accounting.
[PATCH 1/4] as recent CPUs introduce a third running state, after "user" and
"system", we need a new field, "guest", in cpustat to store
[PATCH 1/4] as recent CPUs introduce a third running state, after "user" and
"system", we need a new field, "guest", in cpustat to store the time used by
the CPU to run virtual CPU. Modify /proc/stat to display this new field.
Signed-off-by: Laurent Vivier <[EMAIL PROTECTED]>
--
- [EM
Paul Mackerras <[EMAIL PROTECTED]> writes:
> I'll have to check when that change was done and decide whether we can
> now take out the AT_IGNOREPPC entries. If not it sounds like we need
> to expand AT_VECTOR_SIZE.
I've looked over glibc-2.3 sources (is it old enough? :) and didn't
notice any sp
On Mon, 10 Sep 2007 09:59:57 +0800
Dong_Wei <[EMAIL PROTECTED]> wrote:
> Hi, all.
>I want to dynamically use irqbalance on X86 processor. My design
> is like the following:
>1) if we boot kernel with "noirqbalance", then irqbalance is
> always disabled.
>2) if we boot kernel without "n
On Sun, Sep 09, 2007 at 10:25:54PM +0200, Adrian Bunk wrote:
> On Fri, Aug 31, 2007 at 09:58:22PM -0700, Andrew Morton wrote:
> >...
> > Changes since 2.6.23-rc3-mm1:
> >...
> > git-net.patch
> >...
> > git trees
> >...
>
> This patch makes the following needlessly globalvariables static:
> - sc
On Mon, 10 Sep 2007 11:56:29 +0100
Denys Vlasenko <[EMAIL PROTECTED]> wrote:
>
> Well, if you insist on having it again:
>
> Waiting for atomic value to be zero:
>
> while (atomic_read(&x))
> continue;
>
and this I would say is buggy code all the way.
Not from a pure
On Monday 10 September 2007 10:56, Zhang, Yanmin wrote:
> On Sat, 2007-09-08 at 18:08 +1000, Nick Piggin wrote:
> > On Wednesday 05 September 2007 17:07, Christoph Lameter wrote:
> > > On Wed, 5 Sep 2007, Zhang, Yanmin wrote:
> > > > > slub_max_order=3 slub_min_objects=8
> > > >
> > > > I tried thi
> In thinking about this, I began to wonder about the following. Suppose
> that a (possibly RAID) disk controller correctly reads data from disk and
> has correct data in the controller memory and buffers. However when that
> data is DMA'd into system memory some errors occur (cosmic rays,
>
On Sun, Sep 09, 2007 at 10:25:50PM +0200, Adrian Bunk wrote:
> sctp_addto_param() can become static.
>
> Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
>
ACK, seems reasonable to me.
Neil
--
/***
*Neil Horman
[EMAIL PROTECTED]
*gpg keyid: 1024
Adrian Bunk wrote:
> sctp_addto_param() can become static.
>
> Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
Ack
-vlad
-
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.org/majordomo
On Monday 10 September 2007 13:22, Kyle Moffett wrote:
> On Sep 10, 2007, at 06:56:29, Denys Vlasenko wrote:
> > On Sunday 09 September 2007 19:18, Arjan van de Ven wrote:
> >> On Sun, 9 Sep 2007 19:02:54 +0100
> >> Denys Vlasenko <[EMAIL PROTECTED]> wrote:
> >>
> >>> Why is all this fixation on "v
On Mon, Sep 10, 2007 at 01:55:52PM +0200, Peter Zijlstra wrote:
> On Sun, 2007-09-02 at 20:27 +0200, Nick Piggin wrote:
>
> > Index: linux-2.6/lib/dyndata.c
> > ===
> > --- /dev/null
> > +++ linux-2.6/lib/dyndata.c
> > @@ -0,0 +1,80 @
On Mon, Sep 10, 2007 at 14:39:34 +0100, Alan Cox wrote:
...
> > Well, outpipe-village-512-1.bc.nu is NXDOMAIN.
> > It should have A record 81.2.110.250.
>
> I've yet to see a specification which requires this.
You don't need specs.
My point was you might have better luck emailing people
if you h
On Mon, 10 Sep 2007 16:20:42 +0300
Sami Farin <[EMAIL PROTECTED]> wrote:
> On Mon, Sep 10, 2007 at 13:59:12 +0100, Alan Cox wrote:
> > Will RMK ([EMAIL PROTECTED]) please fix his email setup otherwise I
> > can't send serial/tty/arm stuff to him.
> >
> > "<<< 550 You have no reverse DNS; please t
Dear LKML,
Apologies in advance for potential mis-use of LKML, but I don't know where
else to ask.
An ongoing study on datasets of several Petabytes have shown that there
can be 'silent data corruption' at rates much larger than one might
naively expect from the expected error rates in RAID
On 9/10/07, Greg KH <[EMAIL PROTECTED]> wrote:
> On Mon, Sep 10, 2007 at 01:28:47AM -0400, Dmitry Torokhov wrote:
> > On Sunday 09 September 2007 19:03, Kay Sievers wrote:
> > > On 9/8/07, Anssi Hannula <[EMAIL PROTECTED]> wrote:
> > > >
> > > > However, the change that broke id_path of udev is tha
On Mon, Sep 10, 2007 at 13:59:12 +0100, Alan Cox wrote:
> Will RMK ([EMAIL PROTECTED]) please fix his email setup otherwise I
> can't send serial/tty/arm stuff to him.
>
> "<<< 550 You have no reverse DNS; please try again when you have resolved
Well, outpipe-village-512-1.bc.nu is NXDOMAIN.
It s
Hi Steven, Markus,
On 9/10/07, Steven Rostedt <[EMAIL PROTECTED]> wrote:
>
> --
> On Mon, 10 Sep 2007, Markus Armbruster wrote:
> >
> > I believe this possible, but unlikely (perhaps not so unlikely on
> > virtual machines). Scenarios involve enable succeeding the first
> > time, failing the seco
Avi Kivity wrote:
> Ingo Molnar wrote:
>> * Laurent Vivier <[EMAIL PROTECTED]> wrote:
>>
>>
>>> Ingo, please, could you have a look to these patches ?
>>>
>>> The aim of these four patches is to introduce Virtual Machine time
>>> accounting.
>>>
>>> [PATCH 1/4] as recent CPUs introduce a third ru
Add support for and use the multi-byte NOPs recently documented to be
available on all PentiumPro and later processors.
This patch only applies cleanly on top of the "x86: misc.
constifications" patch sent earlier.
Signed-off-by: Jan Beulich <[EMAIL PROTECTED]>
arch/i386/kernel/alternative.c |
On Mon, 2007-09-10 at 10:31 +0900, Yuichi Nakamura wrote:
> Next is updated patch.
Thanks.
Please include the short description of the patch though when
re-submitting.
> Signed-off-by: Yuichi Nakamura<[EMAIL PROTECTED]>
> ---
> fs/open.c |5 +
> include/linux/secu
Trond Myklebust wrote:
On Sat, 2007-09-08 at 01:56 +0200, Michal Piotrowski wrote:
Hi,
On 07/09/2007, Kamalesh Babulal <[EMAIL PROTECTED]> wrote:
Sep 7 11:42:49 p55lp2 kernel: kernel BUG at fs/nfs/nfs4xdr.c:945!
Sep 7 11:42:49 p55lp2 kernel: Oops: Exception in kernel mode, sig: 5 [#1
Le Fri, 7 Sep 2007 16:37:57 -0700 (PDT),
Jonathan Lim <[EMAIL PROTECTED]> a écrit :
> > Excellent, so can Guillaume change ac_btime to be just
> > tsk->start_time?
>
> I don't think so. Current time (xtime) is relative to the epoch;
> uptime and tsk->start_time (jiffies) are both relative to som
On Mon, Sep 10, 2007 at 01:28:38PM +0100, Ralf Baechle wrote:
> On Sat, Sep 08, 2007 at 09:00:48PM +0100, Jiri Slaby wrote:
>
> > forbid asm/bitops.h direct inclusion
> >
> > Because of compile errors that may occur after bit changes if asm/bitops.h
> > is
> > included directly without e.g. linu
.. as they're, with a single exception, never written to.
Signed-off-by: Jan Beulich <[EMAIL PROTECTED]>
arch/i386/kernel/cpu/perfctr-watchdog.c | 14 --
1 file changed, 8 insertions(+), 6 deletions(-)
--- linux-2.6.23-rc5/arch/i386/kernel/cpu/perfctr-watchdog.c2007-09-07
16:
201 - 300 of 417 matches
Mail list logo
