All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Denys Vlasenko <vda.linux@googlemail.com>,
	Nadav Amit <nadav.amit@gmail.com>
Cc: Nadav Amit <namit@cs.technion.ac.il>, X86 ML <x86@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Testcases for "eip canonical" kvm fixes?
Date: Wed, 11 Mar 2015 15:12:10 +0100	[thread overview]
Message-ID: <55004D3A.2010703@redhat.com> (raw)
In-Reply-To: <CAK1hOcMjh=XSqnsTnxzTO2SAsrXx65v_mgi+gqjk-2LH6Tio+A@mail.gmail.com>



On 11/03/2015 14:27, Denys Vlasenko wrote:
> 
> I'm asking because it seems that stock kernels and stock qemu-kvm
> can't reach code paths you are touching with your fixes.

Some of Nadav's fixes have testcases for it in kvm-unit-tests, and more
can be added.

Paolo

      parent reply	other threads:[~2015-03-11 14:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-10 18:37 Testcases for "eip canonical" kvm fixes? Denys Vlasenko
2015-03-11 13:03 ` Nadav Amit
2015-03-11 13:27   ` Denys Vlasenko
2015-03-11 13:50     ` Nadav Amit
2015-03-11 14:12     ` Paolo Bonzini [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=55004D3A.2010703@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nadav.amit@gmail.com \
    --cc=namit@cs.technion.ac.il \
    --cc=vda.linux@googlemail.com \
    --cc=x86@kernel.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.