qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
	ddm <hope2hope@163.com>,
	qemu-devel@nongnu.org,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Eduardo Habkost" <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] Can not relocate APIC registers address from 0xFEE00000 to self-defined physical addr
Date: Wed, 10 Jul 2019 17:58:53 +0200	[thread overview]
Message-ID: <c7076dee-b401-9595-028e-fc0349e74a7f@redhat.com> (raw)
In-Reply-To: <adefe3b6-f8ff-5010-58e5-45a4445a648f@redhat.com>

On 10/07/19 17:41, Philippe Mathieu-Daudé wrote:
> 
> I wrote a Small OS (based on linux0.11) support SMP, and it can run
> well on bochs, Now i want to migrate it to Qemu, i found that when i
> use wrmsr command to relocate the APIC regsiters addr to a new
> physical address, it can not work, i can not initial APIC timer to
> trigger timer interrupt by the new physical addr just i relocate, but
> when use rdmsr to get APIC base addr has been changed to the new
> physical address, it's strange. In SMP env, if can not relocate APIC
> registers addr for each processor with  different addr, it will
> result in conflict. So, i want to know qemu4.0 whether support
> remaping APIC base address by wrmsr command? if support, please tell
> me how to remap APIC base addr for each processor.

Yes, this is not supported by QEMU.  However, you don't need to change
the base address, because each processor will only write to its own APIC
even if all of them use the same base address.

Paolo


      reply	other threads:[~2019-07-10 15:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-10  7:56 [Qemu-devel] Can not relocate APIC registers address from 0xFEE00000 to self-defined physical addr ddm
2019-07-10 15:41 ` Philippe Mathieu-Daudé
2019-07-10 15:58   ` Paolo Bonzini [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=c7076dee-b401-9595-028e-fc0349e74a7f@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=hope2hope@163.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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).