public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	"Nadav Har'El" <nyh@math.technion.ac.il>,
	kvm <kvm@vger.kernel.org>, Orit Wasserman <owasserm@redhat.com>
Subject: Re: [PATCH v2] KVM: nVMX: Improve I/O exit handling
Date: Thu, 14 Feb 2013 14:11:29 +0200	[thread overview]
Message-ID: <20130214121129.GM9817@redhat.com> (raw)
In-Reply-To: <511CC83E.1080208@siemens.com>

On Thu, Feb 14, 2013 at 12:19:26PM +0100, Jan Kiszka wrote:
> On 2013-02-14 10:32, Gleb Natapov wrote:
> > On Mon, Feb 11, 2013 at 12:19:17PM +0100, Jan Kiszka wrote:
> >> This prevents trapping L2 I/O exits if L1 has neither unconditional nor
> >> bitmap-based exiting enabled. Furthermore, it implements basic I/O
> >> bitmap handling. Repeated string accesses are still reported to L1
> >> unconditionally for now.
> >>
> >> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> >> ---
> >>
> >> Changes in v2:
> >>  - fix two brown-paper-bag bugs (offset for bitmap_b, wrong direction
> >>    of mask shift)
> >>  - use vmcs12 argument instead of get_vmcs12
> >>
> >>  arch/x86/kvm/vmx.c |   54 ++++++++++++++++++++++++++++++++++++++++++++++++++-
> >>  1 files changed, 52 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> >> index fe9a9cf..64e1233 100644
> >> --- a/arch/x86/kvm/vmx.c
> >> +++ b/arch/x86/kvm/vmx.c
> >> @@ -5913,6 +5913,57 @@ static int (*const kvm_vmx_exit_handlers[])(struct kvm_vcpu *vcpu) = {
> >>  static const int kvm_vmx_max_exit_handlers =
> >>  	ARRAY_SIZE(kvm_vmx_exit_handlers);
> >>  
> >> +static bool nested_vmx_exit_handled_io(struct kvm_vcpu *vcpu,
> >> +				       struct vmcs12 *vmcs12)
> >> +{
> >> +	unsigned long exit_qualification;
> >> +	gpa_t bitmap, last_bitmap;
> >> +	bool string, rep;
> >> +	u16 port;
> >> +	int size;
> >> +	u8 b;
> >> +
> >> +	if (nested_cpu_has(vmcs12, CPU_BASED_UNCOND_IO_EXITING))
> >> +		return 1;
> >> +
> >> +	if (!nested_cpu_has(vmcs12, CPU_BASED_USE_IO_BITMAPS))
> >> +		return 0;
> >> +
> >> +	exit_qualification = vmcs_readl(EXIT_QUALIFICATION);
> >> +
> >> +	string = exit_qualification & 16;
> >> +	rep = exit_qualification & 32;
> >> +
> >> +	/* TODO: interpret instruction and check range against bitmap */
> >> +	if (string && rep)
> >> +		return 1;
> >> +
> >> +	port = exit_qualification >> 16;
> >> +	size = (exit_qualification & 7) + 1;
> >> +
> >> +	last_bitmap = (gpa_t)-1;
> >> +	b = -1;
> >> +
> >> +	while (size > 0) {
> >> +		if (port < 0x8000)
> >> +			bitmap = vmcs12->io_bitmap_a;
> >> +		else
> >> +			bitmap = vmcs12->io_bitmap_b;
> >> +		bitmap += (port & 0x7fff) / 8;
> >> +
> >> +		if (last_bitmap != bitmap)
> >> +			kvm_read_guest(vcpu->kvm, bitmap, &b, 1);
> > Return value is ignored.
> 
> Not sure how to map a failure on real HW behaviour. I guess it's best to
Exit to L1 with nested_vmx_failValid() may be?

> simply initialize b to -1 before each call, enforcing an exit on
> unaccessible bitmaps.
> 
I'd just make it explicit:
 if (kvm_read_guest())
    return 1;

> BTW, nested_vmx_exit_handled_msr needs some improvement in this regard, too.
> 
Yes, nested_vmx_exit_handled_msr() use uninitialized 'b' from the stack.
We are leaking host kernel data to a guest here. Patch?

--
			Gleb.

  reply	other threads:[~2013-02-14 12:11 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-10 20:42 [PATCH] KVM: nVMX: Improve I/O exit handling Jan Kiszka
2013-02-11 10:07 ` Nadav Har'El
2013-02-11 10:16   ` Jan Kiszka
2013-02-11 11:19     ` [PATCH v2] " Jan Kiszka
2013-02-14  9:32       ` Gleb Natapov
2013-02-14 11:19         ` Jan Kiszka
2013-02-14 12:11           ` Gleb Natapov [this message]
2013-02-14 12:22             ` Jan Kiszka
2013-02-14 12:56               ` Gleb Natapov
2013-02-14 13:54                 ` Nadav Har'El
2013-02-14 14:44                   ` Gleb Natapov
2013-02-14 18:46         ` [PATCH v3] " Jan Kiszka
2013-02-17  8:55           ` Gleb Natapov
2013-02-18  6:32           ` Jan Kiszka
2013-02-18  6:45             ` [PATCH v4] " Jan Kiszka
2013-02-18  8:44             ` [PATCH v3] " Gleb Natapov
2013-02-18  8:53               ` Jan Kiszka
2013-02-18  8:57                 ` Gleb Natapov
2013-02-18  9:17                   ` [PATCH v5] " Jan Kiszka
2013-02-18  9:36                     ` Gleb Natapov
2013-02-18 10:02                       ` Jan Kiszka
2013-02-18 10:21                         ` [PATCH v6] " Jan Kiszka
2013-02-18 10:32                           ` Gleb Natapov
2013-02-19  2:13                             ` Marcelo Tosatti

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=20130214121129.GM9817@redhat.com \
    --to=gleb@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=nyh@math.technion.ac.il \
    --cc=owasserm@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