linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: stephan.baerwolf@tu-ilmenau.de
Cc: linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: KVM guest-kernel panics double fault
Date: Tue, 10 Jan 2012 12:31:05 +0200	[thread overview]
Message-ID: <4F0C1369.9070607@redhat.com> (raw)
In-Reply-To: <4F0C0EBB.3090506@tu-ilmenau.de>

On 01/10/2012 12:11 PM, Stephan Bärwolf wrote:
> Hello.
>
> Thank you for your lots of information, they helped very much -
> especially debugging...
>
> > The third parameter is actually ecx
> (ebx was actually a typing...  ...of course ecx!)
>
> > The emulator is written to be independent of the rest of kvm, using
> > emul_to_vcpu() undoes that.  If you need access to more vpcu internals,
> > add more function pointers to struct x86_emulate_ops.
> I prepare/adapt everything to the mentioned styles/policy.
> (I'll insert 2 additional ops for getting "cpuid" and "id of vcpu"...)

What do you mean by "id of vcpu"?

>
> > Please post patches separately, not as attachments to a single email. 
> > See Documentation/SubmittingPatches.
> One thing, which is not fully clear to me: Where exactly should I post
> the patches?
> Also to/in this mail/group as an empty mail (containing the patch as
> text-body) per patch?
> Or all (3 patches) at once?

One patch per email, with a cover letter.  Git can help you format and
send them:

  # format three patches, with a cover letter:
  $ git format-patch -3 --cover-letter -n -o patches
  # edit the cover letter:
  $ vi patches/0000-cover-letter-patch
  # post them:
  $ git send-email --to kvm@vger.kernel.org patches/*.patch



-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.


  reply	other threads:[~2012-01-10 10:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-29  1:59 KVM guest-kernel panics double fault Stephan Bärwolf
2011-12-29 10:04 ` Avi Kivity
2012-01-08  2:31   ` Stephan Bärwolf
2012-01-08 10:21     ` Avi Kivity
2012-01-10 10:11       ` Stephan Bärwolf
2012-01-10 10:31         ` Avi Kivity [this message]
2012-01-10 12:17           ` Stephan Bärwolf
2012-01-10 12:34             ` Avi Kivity
2012-01-10 12:48               ` 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=4F0C1369.9070607@redhat.com \
    --to=avi@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stephan.baerwolf@tu-ilmenau.de \
    --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 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).