WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [patch 1/2] HV: allow HVM virtual PICs to have their int

To: "Stephen C. Tweedie" <sct@xxxxxxxxxx>
Subject: Re: [Xen-devel] [patch 1/2] HV: allow HVM virtual PICs to have their interrupt vector reprogrammed
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Fri, 01 Jun 2007 09:02:33 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 01 Jun 2007 00:58:37 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1180643735.6497.25.camel@xxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcekIzVlc6l6yBAWEdyIMAAWy6hiGQ==
Thread-topic: [Xen-devel] [patch 1/2] HV: allow HVM virtual PICs to have their interrupt vector reprogrammed
User-agent: Microsoft-Entourage/11.3.3.061214
On 31/5/07 21:35, "Stephen C. Tweedie" <sct@xxxxxxxxxx> wrote:

> This turned out to be trivial to do.  I was just stalled for a while in
> testing it since it uncovered another regression --- Xen FV seems to
> have problem with the latest dynticks patches from FC7 kernels.
> 
> The new patch is much simpler; at the same time it's uglier in that it's
> an (even more) gross layering violation.
> 
> vmxassist does the rewriting of the guests vPIC vectors, so the HV
> *cannot* have any idea what vectors the guest actually intended to write
> when we go back to 32-bit mode.  However, vmxassist already hard-codes
> the vectors in several places: the 16-bit irq_bases are hard-coded to
> 0x08 and 0x70 in the trap bouncing code, and those bounce traps are
> hard-coded to live at 0x20 and 0x28.  If we are willing to extend that
> hard-coding into the hypervisor (but JUST the existing vmxassist-
> specific portion, not the general vPIC code), then the patch reduces to
> just a few lines, as below.

That's quite nasty, but I think that's okay in this case. I'll apply it.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>
  • Re: [Xen-devel] [patch 1/2] HV: allow HVM virtual PICs to have their interrupt vector reprogrammed, Keir Fraser <=