All of lore.kernel.org
 help / color / mirror / Atom feed
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 19:14:32 +0200	[thread overview]
Message-ID: <4D2C8FF8.5060806@redhat.com> (raw)
In-Reply-To: <AANLkTi=_WTXYGgb3G6eWAkSpfR_=pDC=w9feKtKK8zLV@mail.gmail.com>

On 01/11/2011 06:19 PM, Linus Torvalds wrote:
> On Tue, Jan 11, 2011 at 1:25 AM, Avi Kivity<avi@redhat.com>  wrote:
>> What are your issues with the patch?
> My issues are mainly two-fold:
>
>   - I think "MINOR" is a totally idiotic and meaningless term. It has
> no technical meaning. Why would IO be special? Is it because of
> deadlock concerns with filesystem or block device layer locks? No. And
> it clearly isn't about "sleeping", since a major fault can be
> non-sleeping (think ramdisk, for example).
>
>     Look at the other FAULT_FLAG_xyzzy flags. They have _hard_
> technical reasons. There's no ambiguity. And we ALREADY HAVE the one
> that says "return if it would need to wait", and it's called
> FAULT_FLAG_ALLOW_RETRY.
>

Okay; I'll drop that patch, and look at reusing the existing infrastructure.

> The other issue is:
>
>   - I wasn't aware of this, and clearly not enough other people were
> either, or somebody would have told you that we already had people
> working on the whole FAULT_FLAG_ALLOW_RETRY thing that is much fancier
> and technically superior.
>
> So it simply boils down to the fact that I don't think
> FAULT_FLAG_MAJOR was a good idea. It's badly done, is a total and
> utter hack, and I don't see why I should ever merge it.

And I'll improve the process on core patches as well.


  reply	other threads:[~2011-01-11 17:14 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
2011-01-11 16:19     ` Linus Torvalds
2011-01-11 17:14       ` Avi Kivity [this message]
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=4D2C8FF8.5060806@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 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.