From: Jan Kiszka <jan.kiszka@siemens.com>
To: Joerg Roedel <jroedel@suse.de>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Bandan Das" <bsd@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: Fixing nested SVM event injection
Date: Mon, 13 Jun 2016 11:31:05 +0200 [thread overview]
Message-ID: <575E7D59.2020807@siemens.com> (raw)
In-Reply-To: <20160613092000.GD29948@suse.de>
On 2016-06-13 11:20, Joerg Roedel wrote:
> On Mon, May 23, 2016 at 09:38:42AM +0200, Jan Kiszka wrote:
>> But now I'm loosing interrupts for L2 (keep in mind: under Jailhouse, L1
>> takes no interrupts, only NMIs, L2 will get them all). The pattern is
>> that an interrupt is received and accepted over L1, but I'm not seeing
>> it being injected into L2 after vmrun. What should ensure the injection
>> when switching to guest mode?
>
> Does Jailhouse forward the IRQs from L1 to L2 or will they just
> pass-through? The nested-svm code checks whether the L2 is supposed to
> get the IRQs directly, and injects them if so. At least that is how it
> should work, there might be bugs somewhere...
>
Jailhouse doesn't take any interrupts (just NMIs) and instead allows
them to be injected while the guest runs.
I've started to port the logic we developed and stabilized on Intel for
injecting and cancelling events around L1<->L2 transitions (e.g.
check_nested_events callback). The result was some progress but still
also some lost events. Need to debug this further.
Jan
--
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2016-06-13 9:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 7:38 Fixing nested SVM event injection Jan Kiszka
2016-05-23 11:22 ` Paolo Bonzini
2016-06-13 9:20 ` Joerg Roedel
2016-06-13 9:31 ` Jan Kiszka [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=575E7D59.2020807@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=bsd@redhat.com \
--cc=jroedel@suse.de \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@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