From: Avi Kivity <avi@qumranet.com>
To: David Brown <dmlb2000@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
kvm-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [kvm-devel] [GIT PULL] kvm oops fix
Date: Sun, 22 Apr 2007 08:52:39 +0300 [thread overview]
Message-ID: <462AF827.6020006@qumranet.com> (raw)
In-Reply-To: <9c21eeae0704192154r5abec14ax242f9c40bab09728@mail.gmail.com>
David Brown wrote:
> On 4/19/07, Avi Kivity <avi@qumranet.com> wrote:
>> Linus,
>>
>> Please pull from the 'linus' branch of
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git
>>
>> To get a one-liner fixing a host oops running non-pae guests.
>>
>> Avi Kivity (1):
>> KVM: Fix off-by-one when writing to a nonpae guest pde
>
> Ooo I thought of something else.
> Should this be applied to the current 2.6.20.7 for the next 2.6.20.8
> release?
>
Yes. I'll prepare a patch.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: David Brown <dmlb2000-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Linus Torvalds
<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [GIT PULL] kvm oops fix
Date: Sun, 22 Apr 2007 08:52:39 +0300 [thread overview]
Message-ID: <462AF827.6020006@qumranet.com> (raw)
In-Reply-To: <9c21eeae0704192154r5abec14ax242f9c40bab09728-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
David Brown wrote:
> On 4/19/07, Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org> wrote:
>> Linus,
>>
>> Please pull from the 'linus' branch of
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/avi/kvm.git
>>
>> To get a one-liner fixing a host oops running non-pae guests.
>>
>> Avi Kivity (1):
>> KVM: Fix off-by-one when writing to a nonpae guest pde
>
> Ooo I thought of something else.
> Should this be applied to the current 2.6.20.7 for the next 2.6.20.8
> release?
>
Yes. I'll prepare a patch.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
next prev parent reply other threads:[~2007-04-22 5:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-19 15:50 [GIT PULL] kvm oops fix Avi Kivity
2007-04-19 15:50 ` Avi Kivity
2007-04-19 16:53 ` Linus Torvalds
2007-04-19 16:53 ` Linus Torvalds
2007-04-19 19:09 ` Jeff Garzik
2007-04-19 19:09 ` Jeff Garzik
2007-04-19 19:24 ` [kvm-devel] " David Brown
2007-04-19 19:24 ` David Brown
2007-04-19 19:34 ` [kvm-devel] " Jeff Garzik
2007-04-19 19:34 ` Jeff Garzik
2007-04-19 19:40 ` [kvm-devel] " J. Bruce Fields
2007-04-19 19:40 ` J. Bruce Fields
2007-04-19 20:30 ` Linus Torvalds
2007-04-19 20:30 ` Linus Torvalds
2007-04-19 22:59 ` Linus Torvalds
2007-04-19 22:59 ` Linus Torvalds
2007-04-20 4:54 ` [kvm-devel] " David Brown
2007-04-20 4:54 ` David Brown
2007-04-22 5:52 ` Avi Kivity [this message]
2007-04-22 5:52 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=462AF827.6020006@qumranet.com \
--to=avi@qumranet.com \
--cc=dmlb2000@gmail.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.