From: Avi Kivity <avi@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
KVM list <kvm@vger.kernel.org>
Subject: Re: [GIT PULL] KVM updates for the 2.6.38 merge window
Date: Tue, 11 Jan 2011 11:25:18 +0200 [thread overview]
Message-ID: <4D2C21FE.3000406@redhat.com> (raw)
In-Reply-To: <AANLkTimOOUjXa7WCTirHRrrLfiev4T9iD7spb2VrB_ET@mail.gmail.com>
On 01/10/2011 09:31 PM, Linus Torvalds wrote:
> On Mon, Jan 10, 2011 at 1:21 AM, Avi Kivity<avi@redhat.com> wrote:
> >
> > - asynchronous page faults, which allow a guest to continue processing
> > interrupts even when its memory is being paged in; in the case of a Linux
> > 2.6.38+ guest, it will receive a notification that the host is servicing a
> > page fault, and may switch into another guest process
>
> So quite frankly, I don't like how this was done.
>
> When you touch files like mm/memory.c, you don't just touch them. You
> get sign-offs and acks from the VM maintainers. Seriously.
>
> In this case, I pulled, looked, and then unpulled. I just don't want
> it, and I think the new FAULT_FLAG_MINOR is seriously mis-named and
> hacky.
>
> Is it about atomicity? Is it about IO?
IO. It means, only allow a minor fault; fail for a major fault. Can
you suggest a better name?
> Why wasn't I notified
> before-hand? Was Andrew cc'd?
Andrew and linux-mm were copied. Rik was the only one who reviewed (and
ack'ed) it. I guess I should have explicitly asked for Nick's review.
How do you want to proceed? I can pull this patch out and stub out the
callers in kvm (which will neuter async page faults for the time being,
but we can live with that), then fix it in the background, or we can try
to resolve it now.
What are your issues with the patch?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-01-11 9:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 9:21 [GIT PULL] KVM updates for the 2.6.38 merge window Avi Kivity
2011-01-10 19:31 ` Linus Torvalds
2011-01-11 9:25 ` Avi Kivity [this message]
2011-01-11 16:19 ` Linus Torvalds
2011-01-11 17:14 ` Avi Kivity
2011-01-12 20:33 ` Rik van Riel
2011-01-12 20:53 ` Linus Torvalds
2011-01-13 12:53 ` Gleb Natapov
2011-01-13 15:43 ` Linus Torvalds
2011-01-13 18:58 ` Hugh Dickins
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=4D2C21FE.3000406@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox