public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH] KVM: x86: Save&restore interrupt shadow mask
Date: Mon, 15 Feb 2010 08:33:58 +0200	[thread overview]
Message-ID: <4B78EAD6.2060204@redhat.com> (raw)
In-Reply-To: <4B782D7F.2040102@web.de>

On 02/14/2010 07:06 PM, Jan Kiszka wrote:
>> Needs a KVM_CAP_ and flags bit.
>>      
> Why if merged before 2.6.33? We haven't released KVM_CAP_VCPU_EVENTS yet.
>    

Userspace already knows the interrupt shadow mask free variant.  Maybe 
it all works out, but KVM_CAP_ bits are cheaper than checking (and 
possibly getting it wrong).

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


      reply	other threads:[~2010-02-15  6:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-14 16:49 [PATCH] KVM: x86: Save&restore interrupt shadow mask Jan Kiszka
2010-02-14 16:57 ` Avi Kivity
2010-02-14 17:06   ` Jan Kiszka
2010-02-15  6:33     ` Avi Kivity [this message]

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=4B78EAD6.2060204@redhat.com \
    --to=avi@redhat.com \
    --cc=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    /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