From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Hollis Blanchard <hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: "kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org"
<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
Carsten Otte <cotte-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>,
kvm-ppc-devel
<kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
"Zhang,
Xiantao" <xiantao.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: RFC/patch 2/3 portability: move x86 emulation and mmio device hook to x86.c
Date: Thu, 01 Nov 2007 00:11:17 +0200 [thread overview]
Message-ID: <4728FD85.1090104@qumranet.com> (raw)
In-Reply-To: <1193844770.31610.9.camel@basalt>
Hollis Blanchard wrote:
> On Wed, 2007-10-31 at 02:24 +0200, Avi Kivity wrote:
>
>> For x86 there are two kinds of mmio devices: one is the expected
>> system-wide mmio, and the other is mmio that depends not only on the
>> address, but also on which cpu originated the request. This type is
>> only needed for the local apic.
>>
>> Is the second type also useful for ppc?
>>
>
> Actually yes. At least OpenPIC (one of a variety of interrupt
> controllers used on PowerPC systems) has per-CPU registers:
> A copy of each of these registers will be available to each CPU
> at the same physical address.
>
>
Okay, so we'll have to generalize that code and move it back.
--
Any sufficiently difficult bug is indistinguishable from a feature.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-10-31 22:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1193763784.7800.17.camel@cotte.boeblingen.de.ibm.com>
[not found] ` <1193763784.7800.17.camel-WIxn4w2hgUz3YA32ykw5MLlKpX0K8NHHQQ4Iyu8u01E@public.gmane.org>
2007-10-30 17:44 ` RFC/patch 1/3 portability: move kvm_get/set_msr[_common] to x86.c Carsten Otte
[not found] ` <1193766257.7800.44.camel-WIxn4w2hgUz3YA32ykw5MLlKpX0K8NHHQQ4Iyu8u01E@public.gmane.org>
2007-10-30 18:14 ` Hollis Blanchard
2007-10-30 17:44 ` RFC/patch 2/3 portability: move x86 emulation and mmio device hook " Carsten Otte
[not found] ` <1193766261.7800.45.camel-WIxn4w2hgUz3YA32ykw5MLlKpX0K8NHHQQ4Iyu8u01E@public.gmane.org>
2007-10-30 18:12 ` Hollis Blanchard
2007-10-31 0:24 ` Avi Kivity
[not found] ` <4727CB52.8040501-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-31 15:32 ` Hollis Blanchard
2007-10-31 22:11 ` Avi Kivity [this message]
2007-10-30 17:44 ` RFC/patch 3/3 portability: move pio emulation functions " Carsten Otte
[not found] ` <1193766265.7800.46.camel-WIxn4w2hgUz3YA32ykw5MLlKpX0K8NHHQQ4Iyu8u01E@public.gmane.org>
2007-10-30 18:13 ` Hollis Blanchard
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=4728FD85.1090104@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=cotte-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org \
--cc=hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=xiantao.zhang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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