For one kernel to report a crash another kernel has created we need
to have 2 kernels loaded simultaneously in memory. To accomplish this
the two kernels need to built to run at different physical addresses.
This patch adds the CONFIG_PHYSICAL_START option to the x86 kernel
so we can do just
From: Hariprasad Nellitheertha [EMAIL PROTECTED]
This patch contains the code that enables us to access the previous kernel's
memory as /dev/oldmem.
Signed-off-by: Eric Biederman [EMAIL PROTECTED]
---
Documentation/devices.txt |1
drivers/char/mem.c| 74
This is the x86_64 implementation of the crashkernel option. It reserves
a window of memory very early in the bootup process, so we never use
it for anything but the kernel to switch to when the running
kernel panics.
In addition to reserving this memory a resource structure is registered
so
kernel/crash.c has been renamed kernel/crash_dump.c to clarify it's purpose.
From: Hariprasad Nellitheertha [EMAIL PROTECTED]
This patch provides the interfaces necessary to read the dump contents,
treating it as a high memory device.
Signed off by Hariprasad Nellitheertha [EMAIL PROTECTED]
From: Maciej W. Rozycki [EMAIL PROTECTED]
Fix a kexec problem whcih causes local APIC detection failure.
The problem is detect_init_APIC() is called early, before the command line
have been processed. Therefore lapic (and nolapic) have not been seen,
yet.
Signed-off-by: Maciej W. Rozycki
From: Maciej W. Rozycki [EMAIL PROTECTED]
Rename APIC_MODE_EXINT to APIC_MODE_EXTINT - I think it should be named
after what the mode is called in documentation.
From: Eric W. Biederman [EMAIL PROTECTED]
I have reduced this patch to just the name change in the header. And
integrated the
From: Eric W. Biederman [EMAIL PROTECTED]
This patch disables interrupt generation from the legacy pic on reboot. Now
that there is a sys_device class it should not be called while drivers are
still using interrupts.
There is a report about this breaking ACPI power off on some systems.
From: Eric W. Biederman [EMAIL PROTECTED]
It is ok to reserve resources 4G on x86_64 struct resource is 64bit now :)
Signed-off-by: Eric Biederman [EMAIL PROTECTED]
---
e820.c |2 --
1 files changed, 2 deletions(-)
diff -uNr
For one kernel to report a crash another kernel has created we need
to have 2 kernels loaded simultaneously in memory. To accomplish this
the two kernels need to built to run at different physical addresses.
This patch adds the CONFIG_PHYSICAL_START option to the x86_64 kernel
so we can do
Factor out the apic and smp shutdown code from machine_restart so it can be
called by in the kexec reboot path as well.
Signed-off-by: Eric Biederman [EMAIL PROTECTED]
---
reboot.c | 62 +-
1 files changed, 33 insertions(+), 29
* Peter Chubb [EMAIL PROTECTED] wrote:
Here's a patch that adds the missing read_is_locked() and
write_is_locked() macros for IA64. When combined with Ingo's patch, I
can boot an SMP kernel with CONFIG_PREEMPT on.
However, I feel these macros are misnamed: read_is_locked() returns
true
Rather than batching up entropy samples, resulting in longer lock hold
times when we actually process the samples, mix in samples
immediately. The trickle code should eliminate almost all the
additional interrupt-time overhead this would otherwise incur, with or
without locking.
Signed-off-by:
Remove long-dead md5 code.
Signed-off-by: Matt Mackall [EMAIL PROTECTED]
Index: rnd/drivers/char/random.c
===
--- rnd.orig/drivers/char/random.c 2005-01-18 10:40:00.654809689 -0800
+++ rnd/drivers/char/random.c 2005-01-18
As we no longer allow resizing of pools, it makes sense to allocate
and initialize them statically. Remove create_entropy_store and
simplify rand_initialize.
Signed-off-by: Matt Mackall [EMAIL PROTECTED]
Index: rnd/drivers/char/random.c
When reseeding, we must always do a catastrophic reseed where we
pull enough new bits to make the new state unguessable from outputs
even if we knew the old state. So we must do the checks against the
minimum reseed amount under the pool lock in extract_entropy.
Signed-off-by: Matt Mackall [EMAIL
Put pointer to reseed pool in pool struct and automatically pull
entropy from it if it is set. This lets us remove the
EXTRACT_SECONDARY flag.
Signed-off-by: Matt Mackall [EMAIL PROTECTED]
Index: rnd/drivers/char/random.c
===
---
Move the limit flag to the pool struct, begin process of eliminating
extract flags.
Signed-off-by: Matt Mackall [EMAIL PROTECTED]
Index: rnd/drivers/char/random.c
===
--- rnd.orig/drivers/char/random.c 2005-01-18
* Jack O'Quin [EMAIL PROTECTED] wrote:
Adding a tid field is relatively easy. Fixing the race condition
between setting it in the new thread and using it in the creating
thread is harder, but not impossible. But, even setting it in the new
thread would create an incompatible interface.
I needed to make scsi_mod probe all luns on this device to be able to
use it. After some Googling, it seems it's encouraged to send dmesg
output to this list to get the device added to the list of devices which
should have all luns probed automatically. If I'm mistaken about that,
my apologies.
To enable bootloaders to boot to directly load the x86_64 vmlinux
and to enable the x86_64 kernel to switch into 64bit mode earlier
this patch refactors the x86_64 entry code so there is a native
64bit entry point to the kernel.
I ran this by Andi Kleen and he agreed it looks fairly sane.
Additional parameter to allow keeping an entropy reserve in the input
pool. Groundwork for proper /dev/urandom vs /dev/random starvation prevention.
Signed-off-by: Matt Mackall [EMAIL PROTECTED]
Index: rnd/drivers/char/random.c
===
Clean up buffer usage for SHA and reseed. This makes the code more
readable and reduces worst-case stack usage.
Signed-off-by: Matt Mackall [EMAIL PROTECTED]
Index: rnd/drivers/char/random.c
===
--- rnd.orig/drivers/char/random.c
Break apart extract_entropy into kernel and user versions, remove last
extract flag and some unnecessary variables. This makes the code more
readable and amenable to sparse.
Signed-off-by: Matt Mackall [EMAIL PROTECTED]
Index: rnd/drivers/char/random.c
Jack O'Quin wrote:
Con Kolivas [EMAIL PROTECTED] writes:
This patch for 2.6.11-rc1 provides a method of providing real time
scheduling to unprivileged users which increasingly is desired for
multimedia workloads.
I ran some jack_test3.2 runs with this, using all the default
settings. The
This is a third series of various cleanups for drivers/char/random.c.
It applies on top of the previous 10.
These bits greatly simplify the setup:
1 More meaningful pool names
2 Static allocation of pools
3 Static sysctl bits
These bits make the accounting safer and the code easier to follow:
Give pools more meaningful names.
Signed-off-by: Matt Mackall [EMAIL PROTECTED]
Index: rnd/drivers/char/random.c
===
--- rnd.orig/drivers/char/random.c 2005-01-18 10:21:12.250668976 -0800
+++ rnd/drivers/char/random.c
Static initialization for sysctl support
Signed-off-by: Matt Mackall [EMAIL PROTECTED]
Index: rnd/drivers/char/random.c
===
--- rnd.orig/drivers/char/random.c 2005-01-18 10:36:10.542146558 -0800
+++ rnd/drivers/char/random.c
The vmlinux on x86_64 does not report the correct physical address of
the kernel. Instead in the physical address field it currently
reports the virtual address of the kernel.
This is patch is a bug fix that corrects vmlinux to report the
proper physical addresses.
This is potentially a help
On Wed, 2005-01-19 at 15:11 +1100, Benjamin Herrenschmidt wrote:
We should probably backport that simplification to ppc32...
Yeah I'm increasingly tempted to merge ppc32/ppc64 into one arch
like mips/parisc/s390. Or would that get vetoed on the basis that we
don't have all that horrid non-OF
Andrew the following patchset is against 2.6.11-rc1-mm1 with
all of the kexec patches removed. The list of removed patches
is included below.
This patchsset is a major refresh of the kexec on panic
functionality in the kernel. The primary aim of which was to take
the requirements capture of
Factor out the apic and smp shutdown code from machine_restart so it can be
called by in the kexec reboot path as well.
By switching to the bootstrap cpu by default on reboot I can delete/simplify
some motherboard fixups well.
Signed-off-by: Eric Biederman [EMAIL PROTECTED]
---
reboot.c |
When coming out of apic mode attempt to set the appropriate
apic back into virtual wire mode. This improves on previous versions
of this patch by by never setting bot the local apic and the ioapic
into veritual wire mode.
This code looks at data from the mptable to see if an ioapic has
an
On Wed, 19 Jan 2005, Herbert Xu wrote:
On Tue, Jan 18, 2005 at 01:07:47PM -0500, John W. Linville wrote:
No, that does not fix it. :-( In fact, it doesn't seem to alter the
problem at all...
OK. In that case I agree with your patch. The overruns that I
attributed to it were
This is the x86 implementation of the crashkernel option. It reserves
a window of memory very early in the bootup process, so we never use
it for anything but the kernel to switch to when the running
kernel panics.
In addition to reserving this memory a resource structure is registered
so
This is the i386 implementation of kexec.
Signed-off-by: Eric Biederman [EMAIL PROTECTED]
---
arch/i386/Kconfig | 17 ++
arch/i386/kernel/Makefile |1
arch/i386/kernel/crash.c | 42 +++
arch/i386/kernel/entry.S |2
One of the dangers when switching from one kernel to another
is what happens to all of the other cpus that were running
in the crashed kernel. In an attempt to avoid that problem
this patch adds a nmi handler and attempts to shoot down
the other cpus by sending them non maskable interrupts.
I have addressed the worst of the documentation changes
that come about from the current refacatoring.
From: Hariprasad Nellitheertha [EMAIL PROTECTED]
This patch contains the documentation for the kexec based crash dump tool.
Signed off by Hariprasad Nellitheertha [EMAIL PROTECTED]
This patch removes xfrm_export.c and moves the EXPORT_SYMBOL{,_GPL}'s to
the files where the actual functions are.
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
---
diffstat output:
net/xfrm/Makefile |3 -
net/xfrm/xfrm_algo.c | 12 +++
net/xfrm/xfrm_export.c | 62
Ingo == Ingo Molnar [EMAIL PROTECTED] writes:
Ingo * Peter Chubb [EMAIL PROTECTED] wrote:
Here's a patch that adds the missing read_is_locked() and
write_is_locked() macros for IA64. When combined with Ingo's
patch, I can boot an SMP kernel with CONFIG_PREEMPT on.
However, I feel these
On Tuesday 18 January 2005 10:56, Michal Schmidt wrote:
Hello,
Bill and Nick, could you try the attached patch that I sent to Jens
Axboe yesterday? (You can see the mail with an explanation on
http://marc.theaimsgroup.com/?l=linux-kernelm=110599420505734w=2 )
Michal
Hi
Thanks, this fixes
* Peter Chubb [EMAIL PROTECTED] wrote:
Here's a patch that adds the missing read_is_locked() and
write_is_locked() macros for IA64. When combined with Ingo's
patch, I can boot an SMP kernel with CONFIG_PREEMPT on.
However, I feel these macros are misnamed: read_is_locked() returns
This patch should not make it to the stable kernel without a being
reviewed a lot more. It is unclear how much a hardned kernel can
take when it comes to misconfigured apics. So since a normal kernel
has problems this patch does a clean shutdown.
It is my expectation this patch will be
After the kernel panics if we wish to generate an entire machine core
file it is very nice to know the register state at the time the
machine crashed.
After long discussion it was realized that if you are going to be
saving the information anyway it is reasonable to store the
information in a
Jack O'Quin wrote:
Con Kolivas [EMAIL PROTECTED] writes:
This patch for 2.6.11-rc1 provides a method of providing real time
scheduling to unprivileged users which increasingly is desired for
multimedia workloads.
I ran some jack_test3.2 runs with this, using all the default
settings. The
Hi!
Attached is the dynamic tick patch for x86 to play with
as I promised in few threads earlier on this list.[1][2]
The dynamic tick patch does following:
- Separates timer interrupts from updating system time
- Allows updating time from other interrupts in addition
to timer
Hi!
No, that's fine, we already have to call it before entering the PM
state, so I'll just pass it along and, at the low level, decide how
deep to sleep based on that.
I think I should also add some stats on the amount of interrupts, since
it would be fairly inefficient to keep
This patch was already sent on:
- 9 Nov 2004
Damn, yes. I have it. I don't consider those patches *that* important
that I instantly forward the stuff, they'll go out with the next batch
of v4l updates because it's less work that way.
If you want to have a look at my latest (not submitted
Hi, the following patch:
- correct the err variable tested twice when _NSIG_WORDS == 1
(unlikely to happen, but ..)
- remove some |= in favor of = because we don't need to 'pack' err
Please apply,
Signed-off-by: Vincent Hanquez [EMAIL PROTECTED]
---
Dmitry Torokhov wrote:
Hi,
On Tue, 18 Jan 2005 15:59:35 +0100, Hannes Reinecke [EMAIL PROTECTED] wrote:
Implement proper class names for input drivers.
This patch probably should probably use atomic_inc in case we ever
have non-serialized probe functions.
True.
But the real question is whether we
On Wed, Jan 19, 2005 at 10:43:52AM +0100, Gerd Knorr wrote:
This patch was already sent on:
- 9 Nov 2004
Damn, yes. I have it. I don't consider those patches *that* important
that I instantly forward the stuff, they'll go out with the next batch
of v4l updates because it's less work
On Wed, Jan 19, 2005 at 10:43:52AM +0100, Gerd Knorr wrote:
This patch was already sent on:
- 9 Nov 2004
Damn, yes. I have it. I don't consider those patches *that* important
that I instantly forward the stuff, they'll go out with the next batch
of v4l updates because it's less work
* John Richard Moser [EMAIL PROTECTED] wrote:
There was a kernel-based randomization patch floating around at some
point, though. I think it's part of PaX. That's the one I hated.
PaX and Exec Shield both have them; personally I believe PaX is a more
mature technology, since it's 1)
On Sun, Jan 16, 2005 at 02:13:46PM +0100, Thomas Viehmann wrote:
Hi.
Christoph Hellwig wrote:
Counter-question: What information is available in
/proc/tty/driver/usbserial but not in sysfs?
Thanks for this hint, is there a way of finding vendor and product ids
of all ttyUSB devices
This patch includes the latest changes to the wbsd driver.
Changelog:
* Proper usage of kunmap.
* Comment about hw bugs.
* Waits for data transfers to finish properly.
* Added module version info.
* FIFO bug fix for small reads.
* Optimised FIFO loop.
* DMA demand mode.
* IRQ race condition when
On Tue, Jan 18, 2005 at 10:46:05PM +0100, Lars Marowsky-Bree wrote:
On 2005-01-18T22:18:01, Kiniger, Karl (GE Healthcare) [EMAIL PROTECTED]
wrote:
idea for enhancement of software raid 1:
every time the raid determines that a sector cannot
be read it could at least try to overwrite
It looks like in the 3ware driver the procfs entry /proc/scsi/3w-
has been removed (or actually moved to sysfs).
Unfortunately, this breaks all the (binary only )-: tools provided by
3ware, which are indispensable for system maintenance.
The change came from the driver
On Sun, Jan 16, 2005 at 02:30:33PM -0600, Tom Zanussi wrote:
This would allow an application to write trace events of its own to a
trace stream for instance.
I don't think this is a good idea. Userspace could aswell easily write
its trace into shared memory segments.
Also, I added a
On Sun, Jan 16, 2005 at 01:05:19PM -0600, Tom Zanussi wrote:
One of the things that uses these functions to read from a channel
from within the kernel is the relayfs code that implements read(2), so
taking them away means you wouldn't be able to use read() on a relayfs
file.
Removing them
sa_handler isn't the first member of struct sigaction on mips.
Use C99 initializers to avoid a compiler warning. (There don't
seem to be more serious problems as mips worked with that warning
for ages)
--- 1.33/include/linux/init_task.h 2005-01-05 03:48:20 +01:00
+++
To convert page-index to a byte index you need to cast it to loff_t
first so it's a 64bit value. There have been quite a few places that
got it wrong in the kernel. To make it easier a nice little helper
would be nice, and in fact the NFS code already has it. Let's move it
to pagemap.h so
Hi!
As this patch is related to the VST/High-Res timers, there
are probably various things that can be merged. I have not
yet looked at what all could be merged.
I'd appreciate some comments and testing!
Good news is that it does seem to reduce number of interrupts. Bad
news is that time
Hi Andi,
- set_intr_gate(3,int3);
+ set_system_gate(3,int3);
set_system_gate(4,overflow); /* int4-5 can be called from all */
set_system_gate(5,bounds);
set_intr_gate(6,invalid_op);
Index: linux/arch/x86_64/kernel/kprobes.c
This looks good to me. Andi do you see any
small changes from Linux/MIPS CVS and typedef removal from me
--- 1.12/drivers/scsi/jazz_esp.c2004-08-27 12:34:15 +02:00
+++ edited/drivers/scsi/jazz_esp.c 2005-01-19 12:33:09 +01:00
@@ -6,6 +6,7 @@
* jazz_esp is based on David S. Miller's ESP driver and cyber_esp
*/
+#include
On Wed, Jan 19, 2005 at 11:48:52AM +0100, Kiniger wrote:
...
some random thoughts:
nowadays hardware sector sizes are much bigger than 512 bytes
No :)
and
the read error may affect some sectors +- the sector which actually
returned the error.
That's right
to keep the handling in
Greg KH wrote:
On Tue, Jan 18, 2005 at 05:20:40PM -0500, Dmitry Torokhov wrote:
On Tue, 18 Jan 2005 13:58:20 -0800, Greg KH [EMAIL PROTECTED] wrote:
On Tue, Jan 18, 2005 at 04:49:34PM -0500, Dmitry Torokhov wrote:
On Tue, 18 Jan 2005 13:30:02 -0800, Greg KH [EMAIL PROTECTED] wrote:
On Tue, Jan 18,
Hello Eric,
Eric W. Biederman wrote:
This is the i386 implementation of kexec.
I tried these patches on an i386 box with kexec-tools-1.99.
kexec-ing with vmlinux works fine but bzImage still doesnt
go through. Is there a newer kexec-tools package that we
need to use this with (to take care of
On Wed, Jan 19, 2005 at 05:06:36PM +0530, Prasanna S Panchamukhi wrote:
Hi Andi,
- set_intr_gate(3,int3);
+ set_system_gate(3,int3);
set_system_gate(4,overflow); /* int4-5 can be called from
all */
set_system_gate(5,bounds);
Eric W. Biederman [EMAIL PROTECTED] writes:
[note an extensive review of all this code, but from a quick read...]
+
+static void load_segments(void)
+{
+ __asm__ __volatile__ (
+ \tmovl $STR(__KERNEL_DS),%eax\n
+ \tmovl %eax,%ds\n
+ \tmovl
On Wed, 19 Jan 2005, Christoph Hellwig wrote:
It looks like in the 3ware driver the procfs entry /proc/scsi/3w-
has been removed (or actually moved to sysfs).
Unfortunately, this breaks all the (binary only )-: tools provided by
3ware, which are indispensable for system
On Tue, 18 Jan 2005, Steve Longerbeam wrote:
Why free the shared policy created to split up an old
policy that spans the whole new range? Ie, see patch.
I think you're misreading it. That code comes from when I changed it
over from sp-sem to sp-lock. If it finds that it needs to split an
On Tue, Jan 18, 2005 at 10:39:35PM +0100, Fabio Coatti wrote:
vmstat under load is the following, and config.gz attached. Of course I can
provide any other needed detail; many thanks for any hint.
Looks mightily like DMA is not on, even though you compiled the PIIX driver
in, which lists
David Mosberger wrote:
On Wed, 19 Jan 2005 10:34:30 +1100, Nick Piggin [EMAIL PROTECTED] said:
Nick David I remember you reporting a pipe bandwidth regression,
Nick and I had a patch for it, but that hurt other workloads, so I
Nick don't think we ever really got anywhere. I've recently
* Linus Torvalds [EMAIL PROTECTED] wrote:
The wake_up_sync() hack only helps for the special case where we
know the writer is going to write more. Of course, we could make the
pipe code use that synchronous write unconditionally, and benchmarks
would look better, but I suspect it would hurt
Nick Piggin wrote:
William Lee Irwin III wrote:
It also is used in a particular euphemism that made
it seem odd to me. I suspect it wasn't thought of when it was chosen.
No. What's the euphemism?
... a few private responses later...
Thanks for the enlightenment, everyone. Next time I won't
On Mon, 17 Jan 2005, Tolentino, Matthew E wrote:
I considered adding a new zone but I felt it would be a massive job for
what I considered to be a simple problem. I think my approach is nice
and isolated within the allocator itself and will be less likely to
affect other code.
Just for
Hi,
Here goes the fourth release candidate.
It reverts the root mount retry patch for USB/special devices, this is
going to get fixed cleanly on v2.6.
And updates the i386 defconfig.
v2.4.29 announcement should follow shortly
Summary of changes from v2.4.29-rc3 to v2.4.29-rc4
* Vincent Hanquez [EMAIL PROTECTED] wrote:
Hi, the following patch:
- correct the err variable tested twice when _NSIG_WORDS == 1
(unlikely to happen, but ..)
(this isnt a problem, even if it happens. But worth cleaning up
nevertheless.)
- remove some |= in favor of =
On Mon, 17 Jan 2005, Yasunori Goto wrote:
Is there an architecture-independant way of finding this out?
No. At least, I have no idea. :-(
In another mail to Matthew, I suggested that the zone-free_area_usemap
could be used to track hotplug blocks of pages by either using a
bit-pattern of
Hi Dmitry,
attached is the reworked patch for removing the call to
call_usermodehelper from input.c
I've used the 'phys' attribute to generate the device names, this way we
don't need to touch all drivers and the patch itself is nice and small.
As usual, comments are welcome.
Cheers,
Hannes
--
Hello,
For the relay fork module (I posted it today), I need to execute a
function when a fork occurs. My solution is to add a pointer to a
function (called fork_hook) in the do_fork() and if this pointer isn't
NULL, I call the function. To update the pointer to the function I
export a symbol
Hello,
Here is the relay fork module. It sends a signal to one or several
processes when a fork occurs in the kernel. It relays information about
all forks and not only for a parent from its child like ptrace does.
This module is used by the Enhanced Linux System Accounting
On Tue, 18 Jan 2005, Robert White wrote:
I thought it was not at all unusual to miss a jiffy here or there due
to interrupt
locking/latency; plus jiffies is expressed with respect to the value
of HZ so you
would need to do some deviding in there somewhere.
Makes no difference. The idea is that
Just as a headsup there is a new cleaned up patch here:
http://ck.kolivas.org/patches/SCHED_ISO/2.6.11-rc1-iso-0501192240.diff
The yield bug is still eluding my capture but appears to be related to
the array switch of yielding and rescheduling as ISO after the fact.
Still working on it.
Cheers,
Hi Hannes,
On Wed, 19 Jan 2005 10:59:30 +0100, Hannes Reinecke [EMAIL PROTECTED] wrote:
Dmitry Torokhov wrote:
But the real question is whether we really need class devices have
unique names or we could do with inputX thus leaving individual
drivers intact and only modifying the input
Greg KH [EMAIL PROTECTED] writes:
Ed, I need the following patch against the latest -bk tree in order to
get the aoe code to load and work properly. Does it look good to you?
I'm having trouble seeing what's in -bk. I have a clone of
bk://linux.bkbits.net/linux-2.5, but when I bk pull there
* Benjamin Herrenschmidt ([EMAIL PROTECTED]) wrote:
Hrm... reading more of the patch Martin's previous work, I'm not sure
I like the idea too much in the end... The main problem is that you are
just replaying the ticks afterward, which I see as a problem for
things like sched_clock() which
Dmitry Torokhov wrote:
Hi Hannes,
On Wed, 19 Jan 2005 10:59:30 +0100, Hannes Reinecke [EMAIL PROTECTED] wrote:
Dmitry Torokhov wrote:
But the real question is whether we really need class devices have
unique names or we could do with inputX thus leaving individual
drivers intact and only
Con Kolivas [EMAIL PROTECTED] writes:
Jack O'Quin wrote:
Con Kolivas [EMAIL PROTECTED] writes:
This patch for 2.6.11-rc1 provides a method of providing real time
scheduling to unprivileged users which increasingly is desired for
multimedia workloads.
I ran some jack_test3.2 runs with this,
--
* Building module-init-tools...
./configure --prefix=/usr --host=i486-slackware-linux --mandir=//usr/share/man
--infodir=//usr/share/info --datadir=//usr/share --sysconfdir=//etc
--localstatedir=//var/lib --prefix=/ --enable-zlib
Hi,
This patch moves the memory allocation required by kprobes outside spin lock
as suggested by Andi Kleen. Please let me know your comments.
Thanks
Prasanna
Minor changes to the kprobes code to provide memory allocation
for x86_64 architecture outside kprobes spin lock.
Signed-off-by:
On Wed, 19 Jan 2005 12:56:16 +0100, Hannes Reinecke [EMAIL PROTECTED] wrote:
Greg KH wrote:
On Tue, Jan 18, 2005 at 05:20:40PM -0500, Dmitry Torokhov wrote:
I was mostly talking about the need of 2 separate classes and this
patch lays groundwork for it althou lifetime rules in input system
final:
- 2.4.29-rc4 was released as 2.4.29 with no changes.
Summary of changes from v2.4.29-rc3 to v2.4.29-rc4
Marcelo Tosatti:
o Cset exclude: [EMAIL PROTECTED]|ChangeSet|20041218011100|24870
o Changed VERSION to 2.4.29-rc4
o Update i386
* Ingo Molnar [EMAIL PROTECTED] wrote:
i'm not suggesting that this is the way to go, it's just to test how
nice--20 tasks would perform (on the hacked kernel). We still dont
have this data, because in the other tests you tried, some
non-highprio threads got nice--20 priority as well, which
On Wed, 19 Jan 2005 15:16:08 +0100, Hannes Reinecke [EMAIL PROTECTED] wrote:
Dmitry Torokhov wrote:
Hi Hannes,
On Wed, 19 Jan 2005 10:59:30 +0100, Hannes Reinecke [EMAIL PROTECTED]
wrote:
Dmitry Torokhov wrote:
But the real question is whether we really need class devices have
El mié, 19-01-2005 a las 09:27 +0100, Arjan van de Ven escribió:
On Tue, 2005-01-18 at 23:55 +0100, Lorenzo Hernández García-Hierro
wrote:
Also, maybe an ExecShield specific test (see [1] and [2]) and possibly a
few other tests related with BSD Jails.
[1]:
On Mon, 2005-01-17 at 14:42 +0100, Arjan van de Ven wrote:
The security problems have been addressed, and the namespace-based
approach was never coherently explained. I can't see how such would
work.
see viro's recent proposal for bindmounts and the like.
Is that likely to be usable any
David,
We did talk about looking at using some work Ben did in ppc64 with OF
in ppc32. John Masters was looking into this, but I havent heard much
from him on it lately.
The firmware interface on the ppc32 embedded side is some what broken
in my mind.
- kumar
On Jan 19, 2005, at 1:43 AM,
On Wed, 2005-01-19 at 08:45 -0600, Kumar Gala wrote:
We did talk about looking at using some work Ben did in ppc64 with OF
in ppc32. John Masters was looking into this, but I havent heard much
from him on it lately.
The firmware interface on the ppc32 embedded side is some what broken
in
On Jan 19, 2005, at 8:48 AM, David Woodhouse wrote:
On Wed, 2005-01-19 at 08:45 -0600, Kumar Gala wrote:
We did talk about looking at using some work Ben did in ppc64 with
OF
in ppc32. John Masters was looking into this, but I havent heard
much
from him on it lately.
The firmware
Dmitry Torokhov wrote:
On Wed, 19 Jan 2005 15:16:08 +0100, Hannes Reinecke [EMAIL PROTECTED] wrote:
[ ... ]
I'm not too happy about this 'inputX' thing (as this doesn't carry any
information, whereas 'phys' gives you at least a rough guess what this
device's about), but if phys is to go it would
1 - 100 of 702 matches
Mail list logo
