| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
[Xen-devel] Re: [PATCH 30 of 38] xen: implement io_apic_ops
|
To: |
Ingo Molnar <mingo@xxxxxxx> |
|
Subject: |
[Xen-devel] Re: [PATCH 30 of 38] xen: implement io_apic_ops |
|
From: |
Jeremy Fitzhardinge <jeremy@xxxxxxxx> |
|
Date: |
Thu, 20 Nov 2008 11:38:06 -0800 |
|
Cc: |
Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Campbell <ian.campbell@xxxxxxxxxx>, the arch/x86 maintainers <x86@xxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>, "H. Peter Anvin" <hpa@xxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, Yinghai Lu <yinghai@xxxxxxxxxx> |
|
Delivery-date: |
Thu, 20 Nov 2008 11:38:55 -0800 |
|
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
|
In-reply-to: |
<20081120192218.GF3955@xxxxxxx> |
|
List-help: |
<mailto:xen-devel-request@lists.xensource.com?subject=help> |
|
List-id: |
Xen developer discussion <xen-devel.lists.xensource.com> |
|
List-post: |
<mailto:xen-devel@lists.xensource.com> |
|
List-subscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
|
List-unsubscribe: |
<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
|
References: |
<patchbomb.1226603398@xxxxxxxxxxxxxxxxx> <d103c0da2fa147ac31af.1226603428@xxxxxxxxxxxxxxxxx> <20081120093506.GB6885@xxxxxxx> <492597B9.8070506@xxxxxxxx> <20081120192218.GF3955@xxxxxxx> |
|
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
|
User-agent: |
Thunderbird 2.0.0.17 (X11/20081009) |
Ingo Molnar wrote:
it certainly looks thin enough to me although i'm really not sure we
want to virtualize at the IO-APIC level. Peter, what's your
opinion/preference?
Given that Xen's requirements here are pretty Xen-specific (I don't
imagine that any other virtualization system would work in the same
way), I didn't bother trying to come up with a general "virtualization"
layer at this level - that's why I was pretty blunt about putting xen_*
calls in without any indirection. But the code could certainly be
restructured in a way which would make it simpler to hook Xen as a
side-effect, so long as it was achieving some other goal as well
(general cleanup, big iron architecture support, better msi handling,
whatever...).
J
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
| |
|
Home