* Karsten Wiese <[EMAIL PROTECTED]> wrote:
> this fixes issues like rmmod hanging and inodes leaking.
thanks ... i have reverted the other dcache.c changes as well.
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
did I see a resend of this floating around?
I can't apply this one...
Looks OK though
-
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-info.html
Please read the FAQ
* Akinobu Mita <[EMAIL PROTECTED]> wrote:
> This patch checks register_filesystem() and kern_mount() return
> values.
>
> Cc: Ingo Molnar <[EMAIL PROTECTED]>
> Signed-off-by: Akinobu Mita <[EMAIL PROTECTED]>
thanks.
Acked-by: Ingo Molnar <[EMAIL PROTECTED]>
Ingo
-
To unsubscribe from
Robert Hancock wrote:
The attached patch against 2.6.19-rc6-mm1 fixes some problems in sata_nv
with ATAPI devices on controllers running in ADMA mode. Some of the
logic in the nv_adma_bmdma_* functions was inverted causing a bunch of
warnings and caused those functions not to work properly.
Alan wrote:
More enablebits
Signed-off-by: Alan Cox <[EMAIL PROTECTED]>
applied
-
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-info.html
Please read the FAQ at
Alan wrote:
This patch adds the suspend/resume callbacks for drivers which don't need
any additional help (beyond the pci resume quirk patch I posted earlier
anyway). Also bring version numbers back inline with master copies.
Signed-off-by: Alan Cox <[EMAIL PROTECTED]>
applied this, and
Mikael Pettersson wrote:
On Tue, 21 Nov 2006 16:07:17 -0500, Jeff Garzik wrote:
Mikael Pettersson wrote:
This patch updates the sata_promise driver as follows:
...
Looks pretty decent to me. Two small nits:
1) no_tbg_slew_init should be a bit flag ("1 << 0") inside a 'flags'
variable in
Alan wrote:
This patch adds the suspend/resume callbacks for drivers which don't need
any additional help (beyond the pci resume quirk patch I posted earlier
anyway). Also bring version numbers back inline with master copies.
Signed-off-by: Alan Cox [EMAIL PROTECTED]
applied this, and
Alan wrote:
More enablebits
Signed-off-by: Alan Cox [EMAIL PROTECTED]
applied
-
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-info.html
Please read the FAQ at
* Akinobu Mita [EMAIL PROTECTED] wrote:
This patch checks register_filesystem() and kern_mount() return
values.
Cc: Ingo Molnar [EMAIL PROTECTED]
Signed-off-by: Akinobu Mita [EMAIL PROTECTED]
thanks.
Acked-by: Ingo Molnar [EMAIL PROTECTED]
Ingo
-
To unsubscribe from this list:
* Karsten Wiese [EMAIL PROTECTED] wrote:
this fixes issues like rmmod hanging and inodes leaking.
thanks ... i have reverted the other dcache.c changes as well.
Ingo
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
From: Ingo Molnar [EMAIL PROTECTED]
Subject: [patch] IRQ handler type mismatch for IRQ 14
got this with all SATA/PATA drivers enabled:
Calling initcall 0xc05aceed: legacy_init+0x0/0x5b3()
ata5: PATA max PIO4 cmd 0x170 ctl 0x376 bmdma 0x0 irq 14
IRQ handler type mismatch for IRQ 14
current
Subject: [patch] x86_64: fix earlyprintk=...,keep regression
From: Ingo Molnar [EMAIL PROTECTED]
the following cleanup patch:
commit 2c8c0e6b8d7700a990da8d24eff767f9ca223b96
Author: Andi Kleen [EMAIL PROTECTED]
Date: Tue Sep 26 10:52:32 2006 +0200
[PATCH] Convert x86-64 to early param
* Adrian Bunk [EMAIL PROTECTED] wrote:
This patch contains the following cleanups:
- remove the write-only local variable bandwidth
- don't set max_cache_size in the (cachesize 0) case:
that's already handled in kernel/sched.c:measure_migration_cost()
Signed-off-by: Adrian Bunk [EMAIL
Hi
First of all, thanks for oprofile !
It's the first tool I can really use to profile my app, with a ton of
dynamically loaded plugins and without having to link everything
statically...
But, it there any sane way to use it as non-root user ?
Is there any alternative ?
I'm even thinking of
* Don Mullis [EMAIL PROTECTED] wrote:
This must be a bisection false positive. The patch in question is
essentially a no-op for a UP kernel.
Testing alternately with
1) all -mm1 patches applied, and
2) all except sched-improve-migration-accuracy*.path applied,
confirms
i have released the 2.6.19-rc6-rt8 tree, which can be downloaded from
the usual place:
http://redhat.com/~mingo/realtime-preempt/
lots of fixes are included in -rt8. In particular the inode/dentry leak
found and fixed by Karsten Wiese (and the related OOMs reported by
others) should be
On Mon, Nov 27, 2006 at 11:51:30PM -0800, Don Mullis wrote:
Allow all non-unique call stacks, as judged by pushed sequence of EIPs,
to be to be ignored as failure candidates.
Upon keying in
echo 1 probability
echo 3 verbose
echo -1 times
a few dozen stacks are printk'ed,
On Mon, Nov 27, 2006 at 07:59:40PM +, Alan wrote:
size remains still constant, and the exceeding damaged sectors are
auto-hidden by the drive by means of HPA.
Still incorrect?
Still incorrect. HPA has nothing to do with damaged sectors. The damaged
sectors are replaced from a pool of
Andreas Leitgeb wrote:
On Mon, Nov 27, 2006 at 07:59:40PM +, Alan wrote:
size remains still constant, and the exceeding damaged sectors are
auto-hidden by the drive by means of HPA.
Still incorrect?
Still incorrect. HPA has nothing to do with damaged sectors. The damaged
sectors are
I first need to contact the author of test case if we could send the
test case to open source. The test case is called crashme,
Is that the classical crashme as found in LTP or an enhanced one?
Do you run it in a special way? Is the crash reproducible?
We normally run crashme regularly as
Hi Joe,
Em Seg, 2006-11-27 às 22:36 -0800, Joe Feise escreveu:
Adrian Bunk wrote on 11/27/06 22:07:
On Mon, Nov 27, 2006 at 09:30:27PM -0800, Joe Feise wrote:
Adrian Bunk wrote on 11/25/06 11:15:
But if anyone wants to ever revive this driver, the code is still
present in the older
On Sun, 2006-11-26 at 05:53 +0100, Mike Galbraith wrote:
On Sat, 2006-11-25 at 18:12 +0100, Rafael J. Wysocki wrote:
Hm, could you please file a bugzilla report regarding the serial console for
the information of its maintainer(s)?
Yeah, I'll rummage around a bit first though.
The
Temporarily at
http://userweb.kernel.org/~akpm/2.6.19-rc6-mm2/
Will appear eventually at
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19-rc6/2.6.19-rc6-mm2/
- Added Francois Romieu's Chelsio driver tree, as git-chelsio.patch
Boilerplate:
- See the `hot-fixes'
Dear Alan,
You wrote
The PIIX interface needs CPU intervention each command, so in practice
about every 64K or so, and the CPU gets stalled waiting for the disk
during the setup of each I/O. The newer kernels support AHCI which does
not have this overhead, but it is only present on the newest
not like it's a big deal, but there's a minor incongruity between
the default values for LOG_BUF_SHIFT for IA64 depending on whether
you're configuring for the first time or not.
if i'm configuring with a fresh tree for the first time (so that
there's no .config file) and i run:
$ make
11/27/2006 06:28 PM, Laurent Bigonville wrote/a écrit:
Hi,
I found a thread (about one month old) about an OZ711Mx (O2micro mmc
card reader) driver, but unfortunately it uses some closed-source
code.[1] :(
But I found no thread about the kernel driver for the O2micro PCMCIA
smartcard reader.
...
is it worth trying to bring the Kconfig.debug default values into
line with the defconfig file values, to avoid any possible confusion?
I don't think so.
defconfig is just there to get some working system. You should really
pay attention to the config options you care about, and
On Tue, Nov 28, 2006 at 02:02:46AM -0800, Andrew Morton wrote:
-input-make-serio_register_driver-return-error.patch
-input-check-serio_register_driver-error.patch
-input-change-to-gfp_kernel-for-serio_register_driver-event-allocation.patch
Please drop
On 28/11/06, Fawad Lateef [EMAIL PROTECTED] wrote:
On 11/28/06, Dave Airlie [EMAIL PROTECTED] wrote:
On 11/28/06, Jon Ringle [EMAIL PROTECTED] wrote:
snip
It looks promising, however, I need to reserve a physical address area
that is well known (so that the code running on the other
Hi,
On the Core2 cpus, the rdtsc instruction is not serializing (as defined
in the architecture reference since rdtsc exists) and due to the deep
speculation of these cores, it's possible that you can observe time go
backwards between cores due to this speculation. Since the kernel
already deals
On Tue, 28 Nov 2006 11:09:47 +0100
Martin A. Fink [EMAIL PROTECTED] wrote:
Dear Alan,
You wrote
The PIIX interface needs CPU intervention each command, so in practice
about every 64K or so, and the CPU gets stalled waiting for the disk
during the setup of each I/O. The newer kernels
On Tuesday 28 November 2006 11:28, Arjan van de Ven wrote:
Hi,
On the Core2 cpus, the rdtsc instruction is not serializing (as defined
in the architecture reference since rdtsc exists) and due to the deep
speculation of these cores, it's possible that you can observe time go
backwards
On Tue, 28 Nov 2006, Arjan van de Ven wrote:
...
is it worth trying to bring the Kconfig.debug default values into
line with the defconfig file values, to avoid any possible confusion?
I don't think so. defconfig is just there to get some working
system. You should really pay
Hi,
On Mon, 27 Nov 2006, Lukasz Stelmach wrote:
Greetings.
It seems that someone has broken *conf programs in 2.6.18 because
Unmodified 2.6.18?
only make silentoldconfig recreates autoconf.h and auto.conf
properly after configuration (.config) has changed.
That's correct. The other
Hello,
When CONFIG_MODULE_UNLOAD is not set then this happens:
CC kernel/module.o
kernel/module.c:852: error: `initstate' undeclared here (not in a function)
kernel/module.c:852: error: initializer element is not constant
kernel/module.c:852: error: (near initialization for
Hello,
Agrrh ... tab/spaces thing again. Sorry. Second try:
Signed-off-by: Mariusz Kozlowski [EMAIL PROTECTED]
--- linux-2.6.19-rc6-mm2-a/kernel/module.c 2006-11-28 12:17:09.0
+0100
+++ linux-2.6.19-rc6-mm2-b/kernel/module.c 2006-11-28 12:05:01.0
+0100
@@
Latest version I've published is there:
http://pieleric.free.fr/o2scr/
case OZSCR_OPEN: /* Request ICC */
dprintk(OZSCR_OPEN\n);
ATRLength = ATR_SIZE;
pRdrExt-IOBase = (PSCR_REGISTERS *) dev-io_base; //XXX necessary?
pRdrExt-membase =
It seems I was too eagerly deleting context from my mails.
This made people misunderstand my questions or answer
details that have been clarified in previous mails already.
I did learn quite a lot already about harddisks during this thread.
Thank you to Alan. In particular, about the quantities
On Mon, 27 Nov 2006, Ben Pfaff wrote:
[EMAIL PROTECTED] (David Wagner) writes:
Well, if you want to talk about really high-value keys like the scenarios
you mention, you probably shouldn't be using /dev/random, either; you
should be using a hardware security module with a built-in FIPS
Dear Sir,
This is Kevin Wang from Areca Technology, Tech-Support Team.
as you recommend, we will updated driver/firmware to our ftp/website once it
released.
the firmware V1.42 sent by erich is a beta version and not released yet, it
is certifying still.
so you can not find it in our ftp site or
maybe post once more, and make clear whether you are looking for:
- smart card reader support. (smart card as in digital signature
card.) o2micro creates such readers, they are usualy usb devices,
conform to the ccid standard and work fine (e.g. pcsc-lite plus
ccid driver or openct).
-
Hmm, there are people out there (like me) who still use it and have patched it
to get it working on 2.6.x.
If the maintainer has vanished can you post the patches here instead for
review ?
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
On Mon, Nov 27, 2006 at 10:49:55AM -0800, David Miller ([EMAIL PROTECTED])
wrote:
From: Ulrich Drepper [EMAIL PROTECTED]
Date: Mon, 27 Nov 2006 10:36:06 -0800
David Miller wrote:
Now we'll have to have a compat layer for 32-bit/64-bit environments
thanks to POSIX timers, which is
On Mon, Nov 27, 2006 at 10:20:50AM -0800, Ulrich Drepper ([EMAIL PROTECTED])
wrote:
sigev_value is a union and the largest element is a pointer. So,
transporting the pointer value is sufficient and it should be passed up
to the user in the ptr member of struct ukevent.
That is where I've
On Mon, Nov 27, 2006 at 10:23:39AM -0800, Ulrich Drepper ([EMAIL PROTECTED])
wrote:
Evgeniy Polyakov wrote:
With provided patch it is possible to wakeup 'for-free' - just call
kevent_ctl(ready) with zero number of ready events, so thread will be
awakened if it was in poll(kevent_fd),
On Mon, Nov 27, 2006 at 11:43:46AM -0800, Ulrich Drepper ([EMAIL PROTECTED])
wrote:
Evgeniy Polyakov wrote:
It _IS_ how previous interface worked.
EXACTLY!
No, the old interface committed everything not only up to a given index.
This is the huge difference which makes or breaks
On Mon, Nov 27, 2006 at 11:12:21AM -0800, Ulrich Drepper ([EMAIL PROTECTED])
wrote:
Evgeniy Polyakov wrote:
It just sets hrtimer with abs time and sleeps - it can achieve the same
goals using similar to wait_event() mechanism.
I don't follow. Of course it is somehow possible to wait until
Adrian Bunk [EMAIL PROTECTED] wrote:
This patch moves the EXPORT_SYMBOL's from net/rxrpc/rxrpc_syms.c to the
files with the actual functions.
You can if you like. Can you slap a blank line before each EXPORT_SYMBOL()
though please?
Updated patch below.
Acked-By: David Howells
=
[ INFO: possible irq lock inversion dependency detected ]
2.6.19-rc6 #4
-
nc/1854 just changed the state of lock:
(af_callback_keys + sk-sk_family#2){-.-?}, at: [c0268a7f]
Andreas Leitgeb wrote:
[--snip--]
This theory is backed by my observation of a nearly-broken disk,
that the quantity 3) gradually goes down one step after some time.
The first such step was, when I noticed the problem about half a
year ago, and just recently it stepped down by another one.
Here's another go at an implementation of the arch-neutral GPIO API for
AVR32. I've also thrown in the pin configuration stuff so that you can
see how all the pieces fit together.
Even though it is possible to tell from the hardware whether a pin is
set up for GPIO, I decided to use two
Hello,
Typo fix for 2.6.19-rc6.
--- linux-2.6.19-rc6/fs/ext2/ext2.h2006-11-20 19:25:16.0 +0100
+++ linux-2.6.19-rc6.fixed/fs/ext2/ext2.h2006-11-28 10:39:04.0
+0100
@@ -27,7 +27,7 @@
/*
* i_block_group is the number of the block group which
On Mon, 27 Nov 2006, Jon Ringle wrote:
Robert Hancock wrote:
Jon Ringle wrote:
Hi,
I need to reserve a page of memory at a specific area of RAM that will
be used as a shared memory with another processor over PCI. How can I
ensure that the this area of RAM gets reseved so that the Linux's
Continuing the tangent:
Henrique de Moraes Holschuh wrote:
On Mon, 27 Nov 2006, Ben Pfaff wrote:
[EMAIL PROTECTED] (David Wagner) writes:
Well, if you want to talk about really high-value keys like the scenarios
you mention, you probably shouldn't be using /dev/random, either; you
should
On Mon, 2006-11-27 at 10:49 +0100, Ingo Molnar wrote:
i have released the 2.6.19-rc6-rt8 tree, which can be downloaded from
the usual place:
http://redhat.com/~mingo/realtime-preempt/
Hi, yesterday I have done a yum -y update and have installed rt7.
I test it with success, boot without
On a custom board with ds1337 RTC I found that upgrade from 2.6.15 to
2.6.18 broke RTC support.
The main problem are changes to ds1337_init_client().
When a ds1337 recognizes a problem (e.g. power or clock failure) bit 7
in status register is set. This has to be reset by writing 0 to status
Hello!
- Whether you automatically bump up the entropy estimate when
root users write to /dev/random is a design choice where you could
reasonably go either way. On the one hand, you might want to ensure
that root has to take some explicit action to allege that it is
This a set of fixes mostly to make the driver actually work:
1. Actually select the line for setting parameters and receiver
disable/enable.
2. Select the line for receive and transmit interrupt handling correctly.
3. Report the transmitter empty state correctly.
4. Set the I/O type of ports
On Mon, 27 Nov 2006, Rohit Seth wrote:
Hi Mel,
On Mon, 2006-11-27 at 13:18 +, Mel Gorman wrote:
On Wed, 22 Nov 2006, Rohit Seth wrote:
This patch provides a IO hole size in a given address range.
Hi,
This patch reintroduces a function that doubles up what
On 2006-11-27 23:52, Kyle Moffett wrote:
Actually, our current /dev/random implementation is secure even if the
cryptographic algorithms can be broken under traditional circumstances.
This is far from obvious, and in my opinion incorrect. David explained
this very well in his follow-up. Other
On Mon, 27 Nov 2006, Jun Sun wrote:
On Mon, Nov 27, 2006 at 08:58:57AM -0500, linux-os (Dick Johnson) wrote:
I think it probably resets the instant that you turn off paging. To
turn off paging, you need to copy some code (properly linked) to an
area where there is a 1:1 mapping between
This fixes a problem with gcc4 mis-compiling the stack unwind code under
-Os, which resulted in 'stuck' messages whenever an assembly routine was
encountered.
(The second hunk is trivial cleanup.)
Signed-off-by: Jan Beulich [EMAIL PROTECTED]
--- linux-2.6.19-rc6/kernel/unwind.c2006-11-22
Linus, please do an update from:
http://www.kernel.org/pub/scm/linux/kernel/git/perex/alsa.git
(linus branch)
The GNU patch is available at:
ftp://ftp.alsa-project.org/pub/kernel-patches/alsa-git-2006-11-28.patch.gz
Additional notes:
This update contains only serious fixes.
The
On Tue, Nov 28, 2006 at 02:12:24PM +, Jan Beulich wrote:
This fixes a problem with gcc4 mis-compiling the stack unwind code under
-Os, which resulted in 'stuck' messages whenever an assembly routine was
encountered.
mis-compiling and work around are wrong words, the code had undefined
On Mon, Nov 27, 2006 at 03:40:35PM -0700, Eric W. Biederman wrote:
Herbert Poetzl [EMAIL PROTECTED] writes:
the linux banner needs some attention too, when I get
around, I'll send a patch for that ...
In what sense?
I have trouble seeing the banner printed at bootup as being
mis-compiling and work around are wrong words, the code had undefined
behavior (there is no sequence point between evaluation of ptr and
get_uleb128(ptr, end) and ptr is modified twice, so the compiler can
evaluate it e.g. as:
temp = ptr;
temp = temp + get_uleb128(ptr, end);
ptr = temp;
or
temp =
Eric Sandeen wrote:
We saw problems w/ xfs doing AIO+DIO into a sparse file.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=217098
It seemed that xfs was doing extent conversion at the wrong offsets, so
written regions came up as unwritten (zeros) and stale data was exposed
in the region
On Tue, Nov 28, 2006 at 02:48:15PM +, Jan Beulich wrote:
I disagree - the standard says there's a sequence point at a function
call after evaluating all function arguments. To me this means that any
That's true, that sequence point makes sure e.g. all side effects such as
Herbert Poetzl [EMAIL PROTECTED] writes:
On Mon, Nov 27, 2006 at 03:40:35PM -0700, Eric W. Biederman wrote:
Herbert Poetzl [EMAIL PROTECTED] writes:
the linux banner needs some attention too, when I get
around, I'll send a patch for that ...
In what sense?
I have trouble seeing the
Hi,
One of my NFS servers just gave me a nasty surprise that I think it is
relevant to tell you about:
Filesystem dm-1: XFS internal error xfs_trans_cancel at line 1138 of
file fs/xfs/xfs_trans.c. Caller 0x8034b47e
Call Trace:
[8020b122] show_trace+0xb2/0x380
Patch from Dmitry Monakhov:
Previous fix for retries in ext3_prepare_write() violation
was a bit errorneuos:
- it missed return of error code from ext3_journal_stop()
- it missed do_journal_get_write_access() before commit_write
a few comments added also.
Signed-Off-By: Dmitry Monakhov [EMAIL
On Tue, Nov 28, 2006 at 08:38:25AM -0700, Eric W. Biederman wrote:
Herbert Poetzl [EMAIL PROTECTED] writes:
On Mon, Nov 27, 2006 at 03:40:35PM -0700, Eric W. Biederman wrote:
Herbert Poetzl [EMAIL PROTECTED] writes:
the linux banner needs some attention too, when I get
around, I'll
On Tuesday 28 November 2006 15:12, Jan Beulich wrote:
This fixes a problem with gcc4 mis-compiling the stack unwind code under
-Os, which resulted in 'stuck' messages whenever an assembly routine was
encountered.
(The second hunk is trivial cleanup.)
Thanks for finally nailing that bug.
Martin Mares wrote:
More importantly, it should be possible for root to write to /dev/random
_without_ increasing the entropy count, for example when restoring random
pool contents after reboot. In such cases you want the pool to contain
at least some unpredictable data before real entropy
Hello!
After a reboot the entropy estimate starts at zero, so if you are adding
data to the pool from the previous boot, you DO want the estimate to
increase because you are, in fact, adding entropy.
I'm adding entropy, but unless I record the exact amount of entropy when
dumping the pool,
On Wed, 2006-11-22 at 06:06 -0800, Mark Knecht wrote:
Ingo,
I started building the new kernels a few days ago with your
2.6.19-rc6-rt0 announcement. The kernels have built fine but so far I
am unable to build the realtime-lsm package against them so no reason
to reboot.
I know there
Hi,
I have a looong time opened a bugreport on XFS at
http://bugzilla.kernel.org/show_bug.cgi?id=7287 and I see it still
appear in my kernel output during bootup. I guess this is one of the
relatively new kernel self-testing features introduced recently. I
just wanted to let you know about that.
Martin Mares wrote:
I'm adding entropy, but unless I record the exact amount of entropy when
dumping the pool, I don't know how much I am adding, so using any fixed
number is obviously wrong.
You aren't dumping and restoring the entropy pool; you are dumping
random data generated by the pool,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jesper Juhl escreveu:
Oct 7 18:25:00 laverne kernel: PCI: Bus #04 (-#07) is hidden behind
transparent bridge #02 (-#04) (try 'pci=assign-busses')
Oct 7 18:25:00 laverne kernel: Please report the result to
linux-kernel to
fix this permanently
First, please don't remove the Cc: list.
David Wagner wrote:
Sorry, but I disagree with just about everything you wrote in this
message. I'm not committing any logical fallacies. I'm not assuming
it works because it would be a bug if it didn't; I'm just trying to
Nope, I don't think so.
On Thu, 2006-11-23 at 18:21 +0300, realales wrote:
Also I analyzed XTEST sources without any success.
I know that this is unlikely the right place to ask this but could
someone please point me on the right way to move further?! Or may it
be already a know problem for somebody?
Sounds like a
Hello,
Today I had to debug a kernel of a remote machine that has no IPMI
or serial console attached to it. So I sat for two hours and cooked
a support for interacting with KDB purely over the network, by
extending netconsole.
The result is very adhoc-ish in nature, but it works nicely. Your
* Avi Kivity [EMAIL PROTECTED] wrote:
--- linux-2.6.orig/drivers/kvm/kvm.h
+++ linux-2.6/drivers/kvm/kvm.h
please move this from drivers/kvm/ to kernel/kvm/ [or even into a
toplevel kvm/ directory] - KVM is not a driver, KVM enhances the core
Linux kernel with hypervisor functionality.
This patchset adds support for AMD processors with SVM (or AMD-V)
technology.
KVM on AMD is fairly fast despite the naive mmu implementation. It
should also support many more guests, since the real mode implementation
on AMD is complete.
The bulk of the work was performed by Yaniv; I
Add a couple of missing mmu flushes. The Intel tlb is too coarse to be
affected, but they are necessary for AMD.
Signed-off-by: Yaniv Kamay [EMAIL PROTECTED]
Signed-off-by: Avi Kivity [EMAIL PROTECTED]
Index: linux-2.6/drivers/kvm/mmu.c
This adds the AMD specific vcpu structure.
Signed-off-by: Yaniv Kamay [EMAIL PROTECTED]
Signed-off-by: Avi Kivity [EMAIL PROTECTED]
Index: linux-2.6/drivers/kvm/kvm.h
===
--- linux-2.6.orig/drivers/kvm/kvm.h
+++
Add decoding support for the few instructions AMD SVM does not decode itself,
and corresponding entries in the arch function vector. They will never
be called on Intel machines.
The invlpg instruction is a special case: unlike other instructions with
the same main opcode, it may not fetch data
Wire it all up and we're ready to go.
Signed-off-by: Avi Kivity [EMAIL PROTECTED]
Index: linux-2.6/drivers/kvm/Kconfig
===
--- linux-2.6.orig/drivers/kvm/Kconfig
+++ linux-2.6/drivers/kvm/Kconfig
@@ -24,3 +24,10 @@ config KVM_INTEL
This patch adds definitions for the structures and constants defined by
the AMD SVM extensions.
It also adds definitions for the three SVM instructions, so that we do not
depend on newer assemblers.
Signed-off-by: Yaniv Kamay [EMAIL PROTECTED]
Signed-off-by: Avi Kivity [EMAIL PROTECTED]
Index:
Implement the kvm function vector.
Signed-off-by: Yaniv Kamay [EMAIL PROTECTED]
Signed-off-by: Avi Kivity [EMAIL PROTECTED]
Index: linux-2.6/drivers/kvm/svm.c
===
--- /dev/null
+++ linux-2.6/drivers/kvm/svm.c
@@ -0,0 +1,1622 @@
+/*
The clgi, stgi, and invlpga instructions are all too new to unleash on
the world's assemblers. Replace them with the opcode sequences.
Signed-off-by: Avi Kivity [EMAIL PROTECTED]
diff -X /home/avi/kvm/linux-2.6/Documentation/dontdiff --exclude=Makefile -ru
http://kvm.sourceforge.net
Changes:
- AMD SVM support (x86-64 hosts only)
- Preliminary live migration support
- 'make install' also installs kernel modules, if selected
- random fixes
The kernel package in this release produces three modules: kvm.ko,
kvm-intel.ko, and kvm-amd.ko. To use
ext2_new_blocks has a nice io_error label for setting -EIO,
so goto that in the one place that doesn't already use it.
Signed-off-by: Hugh Dickins [EMAIL PROTECTED]
---
fs/ext2/balloc.c |7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
--- 2.6.19-rc6-mm2/fs/ext2/balloc.c
rsv_end is the last block within the reservation,
so alloc_new_reservation should accept start_block == rsv_end as success.
Signed-off-by: Hugh Dickins [EMAIL PROTECTED]
---
fs/ext2/balloc.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- 2.6.19-rc6-mm2/fs/ext2/balloc.c
After several days of testing ext2 with reservations, it got caught inside
ext2_try_to_allocate_with_rsv: alloc_new_reservation repeatedly succeeding
on the window [12cff,12d0e], ext2_try_to_allocate repeatedly failing to
find the free block guaranteed to be included (unless there's contention).
ext2_new_blocks should reset the reservation window size to 0 when squeezing
the last blocks out of an almost full filesystem, so the retry doesn't skip
any groups with less than half that free, reporting ENOSPC too soon.
Signed-off-by: Hugh Dickins [EMAIL PROTECTED]
---
fs/ext2/balloc.c |1
grp_goal 0 is a genuine goal (unlike -1),
so ext2_try_to_allocate_with_rsv should treat it as such.
Signed-off-by: Hugh Dickins [EMAIL PROTECTED]
---
fs/ext2/balloc.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- 2.6.19-rc6-mm2/fs/ext2/balloc.c 2006-11-24
The reservations tree is an rb_tree not a list, so it's less confusing to
use rb_entry() than list_entry() - though they're both just container_of().
Signed-off-by: Hugh Dickins [EMAIL PROTECTED]
---
fs/ext2/balloc.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
---
On Tue, 28 Nov 2006 01:38:19 -0500 Dave Jones wrote:
On Tue, Nov 28, 2006 at 01:27:47AM -0500, Dave Jones wrote:
arch/i386/mach-generic/built-in.o: In function `apicid_to_node':
include/asm/mach-summit/mach_apic.h:90: undefined reference to
`apicid_2_node'
config is at
301 - 400 of 614 matches
Mail list logo
