From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Yang, Sheng" <sheng.yang@intel.com>
Cc: kvm-devel <kvm@vger.kernel.org>
Subject: LAPIC soft-disable vs. LVT masking
Date: Mon, 20 Oct 2008 10:49:11 +0200 [thread overview]
Message-ID: <48FC4607.10803@siemens.com> (raw)
Hi Sheng,
obviously, I meditated too long over the APIC specs and VAPIC code of
KVM: When the guest resets the soft-enable bit in SVR, the in-kernel
APIC implementation also set the LVT masked bits - so far, so fine
(according to specs). But I failed to read out of that doc if those mask
bits are permanently set (until the guest clears them again) or only
until the soft-disabling ends (ie. they are restored to their previous
state - QEMU goes this way). Can you clarify?
Thanks,
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next reply other threads:[~2008-10-20 8:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 8:49 Jan Kiszka [this message]
2008-10-20 9:46 ` LAPIC soft-disable vs. LVT masking Yang, Sheng
2008-10-20 11:31 ` Sheng Yang
2008-10-20 11:58 ` Jan Kiszka
2008-10-20 12:16 ` Sheng Yang
2008-10-20 12:21 ` Jan Kiszka
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=48FC4607.10803@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=sheng.yang@intel.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