From: Jan Kiszka <jan.kiszka@web.de>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [RFC][PATCH] apic: Fix relocation
Date: Thu, 03 Feb 2011 22:24:26 +0100 [thread overview]
Message-ID: <4D4B1D0A.5090901@web.de> (raw)
In-Reply-To: <AANLkTinJy01sM29TPF6H_9NmBim7VD68dEa1yVs1OMj3@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4978 bytes --]
On 2011-02-03 20:43, Blue Swirl wrote:
> On Thu, Feb 3, 2011 at 7:32 PM, Jan Kiszka <jan.kiszka@siemens.com> wrote:
>> When the guest remaps an APIC by modifying MSR_IA32_APICBASE, we need to
>> update its mmio mapping. This is a bit tricky as multiple APICs might be
>> mapped to the same address. So walk through the full list to avoid
>> unmapping a region that is still in use.
>>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>> ---
>>
>> RFC as I did not yet have a chance to test actual relocation. Standard
>> OSes don't do this, otherwise we would have noticed this earlier.
>>
>> hw/apic.c | 38 +++++++++++++++++++++++++++++++++++++-
>> hw/pc.c | 10 ----------
>> 2 files changed, 37 insertions(+), 11 deletions(-)
>>
>> diff --git a/hw/apic.c b/hw/apic.c
>> index 05a115f..b64af59 100644
>> --- a/hw/apic.c
>> +++ b/hw/apic.c
>> @@ -294,6 +294,40 @@ void apic_deliver_irq(uint8_t dest, uint8_t dest_mode,
>> trigger_mode);
>> }
>>
>> +static void apic_update_mapping(APICState *s)
>> +{
>> + target_phys_addr_t new_addr;
>> + bool overlap = false;
>> + APICState *apic_iter;
>> + int i;
>> +
>> + for (i = 0; i < MAX_APICS; i++) {
>> + apic_iter = local_apics[i];
>> + if (!apic_iter || apic_iter == s) {
>> + continue;
>> + }
>> + if ((apic_iter->apicbase & MSR_IA32_APICBASE_BASE) ==
>> + s->busdev.mmio[0].addr) {
>> + overlap = true;
>> + break;
>> + }
>> + }
>> + if (overlap) {
>> + /*
>> + * As APICs are pre-CPU devices, they may have identical base
>> + * addresses. We must avoid unregistering an old io-region that is
>> + * still in use by another APIC.
>> + */
>> + s->busdev.mmio[0].addr = (target_phys_addr_t)-1;
>> + }
>> + if (s->apicbase & MSR_IA32_APICBASE_ENABLE) {
>> + new_addr = s->apicbase & MSR_IA32_APICBASE_BASE;
>> + } else {
>> + new_addr = (target_phys_addr_t)-1;
>> + }
>> + sysbus_mmio_map(&s->busdev, 0, new_addr);
>> +}
>> +
>> void cpu_set_apic_base(DeviceState *d, uint64_t val)
>> {
>> APICState *s = DO_UPCAST(APICState, busdev.qdev, d);
>> @@ -302,7 +336,7 @@ void cpu_set_apic_base(DeviceState *d, uint64_t val)
>>
>> if (!s)
>> return;
>> - s->apicbase = (val & 0xfffff000) |
>> + s->apicbase = (val & MSR_IA32_APICBASE_BASE) |
>> (s->apicbase & (MSR_IA32_APICBASE_BSP | MSR_IA32_APICBASE_ENABLE));
>> /* if disabled, cannot be enabled again */
>> if (!(val & MSR_IA32_APICBASE_ENABLE)) {
>> @@ -310,6 +344,7 @@ void cpu_set_apic_base(DeviceState *d, uint64_t val)
>> cpu_clear_apic_feature(s->cpu_env);
>> s->spurious_vec &= ~APIC_SV_ENABLE;
>> }
>> + apic_update_mapping(s);
>> }
>>
>> uint64_t cpu_get_apic_base(DeviceState *d)
>> @@ -948,6 +983,7 @@ static void apic_reset(DeviceState *d)
>> bsp = cpu_is_bsp(s->cpu_env);
>> s->apicbase = 0xfee00000 |
>> (bsp ? MSR_IA32_APICBASE_BSP : 0) | MSR_IA32_APICBASE_ENABLE;
>> + apic_update_mapping(s);
>
> Here the device maps itself at reset, which is not OK.
>
>>
>> apic_init_reset(d);
>>
>> diff --git a/hw/pc.c b/hw/pc.c
>> index 4dfdc0b..294aa66 100644
>> --- a/hw/pc.c
>> +++ b/hw/pc.c
>> @@ -859,7 +859,6 @@ static DeviceState *apic_init(void *env, uint8_t apic_id)
>> {
>> DeviceState *dev;
>> SysBusDevice *d;
>> - static int apic_mapped;
>>
>> dev = qdev_create(NULL, "apic");
>> qdev_prop_set_uint8(dev, "id", apic_id);
>> @@ -867,15 +866,6 @@ static DeviceState *apic_init(void *env, uint8_t apic_id)
>> qdev_init_nofail(dev);
>> d = sysbus_from_qdev(dev);
>>
>> - /* XXX: mapping more APICs at the same memory location */
>> - if (apic_mapped == 0) {
>> - /* NOTE: the APIC is directly connected to the CPU - it is not
>> - on the global memory bus. */
>> - /* XXX: what if the base changes? */
>> - sysbus_mmio_map(d, 0, MSI_ADDR_BASE);
>> - apic_mapped = 1;
>
> TBH, this is not so cool either. Maybe APIC should not be a Sysbus
> device at all.
You actually need the APIC to A) be part of or a child of its CPU and B)
be part of a second, APIC bus (where we would find IOAPICs as well, also
multi-homed). We don't model this ATM, so we have global local_apics[]
and soon ioapics[]. And we need to coordinate remapping of the APIC
where we have those full views.
But even that's not the actual problem. The problem here is that we need
per-CPU MMIO mapping and handling here, and that is not supported by
QEMU. We would furthermore have to refactor everything around apicbase
updates, and I surely don't want to do this in this fix. It targets the
obvious breakage based on the current QEMU architecture. We can always
improve on top of course.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
prev parent reply other threads:[~2011-02-03 21:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 19:32 [Qemu-devel] [RFC][PATCH] apic: Fix relocation Jan Kiszka
2011-02-03 19:43 ` [Qemu-devel] " Blue Swirl
2011-02-03 21:24 ` 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=4D4B1D0A.5090901@web.de \
--to=jan.kiszka@web.de \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.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).