From: Marcelo Tosatti <mtosatti@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>, stephan.baerwolf@tu-ilmenau.de
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 0/2] KVM guest-kernel panics double fault
Date: Fri, 13 Jan 2012 08:13:25 -0200 [thread overview]
Message-ID: <20120113101325.GA25595@amt.cnet> (raw)
In-Reply-To: <4F0F02B1.8080508@siemens.com>
On Thu, Jan 12, 2012 at 04:56:33PM +0100, Jan Kiszka wrote:
> > Stephan Baerwolf (2):
> > KVM: extend "struct x86_emulate_ops" with "get_cpuid"
> > KVM: fix missing "illegal instruction"-trap in protected modes
> >
> > arch/x86/include/asm/kvm_emulate.h | 19 ++++++++
> > arch/x86/kvm/emulate.c | 80
> > ++++++++++++++++++++++++++++++++++-
> > arch/x86/kvm/x86.c | 21 +++++++++
> > 3 files changed, 117 insertions(+), 3 deletions(-)
> >
>
> linux/scripts/checkpatch.pl can help identifying remaining style violations.
>
> Moreover, when sending your patches via Thunderbird, you first need to
> make sure that you have its line wrapping under control. "Toggle Word
> Wrap" helps me for single patches. But for series, I prefer (scripted)
> git format-patch/send-email.
Applied a cleanup up version of these patches. Thanks Stephan.
http://git.kernel.org/?p=virt/kvm/kvm.git;a=commit;h=0769c5de24621141c953fbe1f943582d37cb4244
http://git.kernel.org/?p=virt/kvm/kvm.git;a=commit;h=e28ba7bb020f07193bc000453c8775e9d2c0dda7
next prev parent reply other threads:[~2012-01-13 10:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4EFBC973.1040905@tu-ilmenau.de>
[not found] ` <4EFC3B17.1040601@redhat.com>
[not found] ` <4F09001D.1050701@tu-ilmenau.de>
[not found] ` <4F096E26.4090201@redhat.com>
[not found] ` <4F0C0EBB.3090506@tu-ilmenau.de>
[not found] ` <4F0C1369.9070607@redhat.com>
[not found] ` <4F0C2C4E.3000703@tu-ilmenau.de>
[not found] ` <4F0C3044.7050307@redhat.com>
[not found] ` <4F0C33A0.6080509@tu-ilmenau.de>
2012-01-10 14:26 ` [PATCH 0/2] KVM guest-kernel panics double fault Stephan Bärwolf
2012-01-10 14:26 ` [PATCH 1/2] KVM: extend "struct x86_emulate_ops" with "get_cpuid" Stephan Bärwolf
2012-01-10 14:26 ` [PATCH 2/2] KVM: fix missing "illegal instruction"-trap in protected modes Stephan Bärwolf
2012-01-11 19:09 ` Marcelo Tosatti
2012-01-11 20:01 ` Stephan Bärwolf
2012-01-11 21:21 ` Marcelo Tosatti
2012-01-11 22:19 ` Stephan Bärwolf
2012-01-12 10:47 ` Marcelo Tosatti
2012-01-12 15:43 ` [PATCH 0/2] KVM guest-kernel panics double fault Stephan Bärwolf
2012-01-12 15:56 ` Jan Kiszka
2012-01-13 10:13 ` Marcelo Tosatti [this message]
2012-01-15 19:44 ` Stephan Bärwolf
2012-01-16 9:58 ` Marcelo Tosatti
2012-01-16 11:24 ` Stephan Bärwolf
2012-01-12 15:43 ` [PATCH 1/2] KVM: extend "struct x86_emulate_ops" with "get_cpuid" Stephan Bärwolf
2012-01-12 15:43 ` [PATCH 2/2] KVM: fix missing "illegal instruction"-trap in protected modes Stephan Bärwolf
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=20120113101325.GA25595@amt.cnet \
--to=mtosatti@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=stephan.baerwolf@tu-ilmenau.de \
/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;
as well as URLs for NNTP newsgroup(s).