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

[Xen-devel] RE: vtsc in domain builder

To: "Xen-Devel (E-mail)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] RE: vtsc in domain builder
From: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Date: Tue, 15 Sep 2009 16:32:50 -0700 (PDT)
Cc: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Tue, 15 Sep 2009 16:33:32 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <e827d4c9-e2f8-4232-bfe1-1440ee30098d@default>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> Was this change due to some backward compatibility reason?

I found the compatibility issue describe here:

http://xen.markmail.org/message/usjxnjyp3csm3uct?q=superpages+date:200907

So it seems even more important that I somehow claim
a field (or at least a bit) in struct xc_dom_image.
Any help to get this right would be appreciated
as getting it wrong clearly has some non-obvious
consequences.

Thanks,
Dan

> -----Original Message-----
> From: Dan Magenheimer 
> Sent: Tuesday, September 15, 2009 3:58 PM
> To: Xen-Devel (E-mail)
> Subject: vtsc in domain builder
> 
> 
> I'm working on passing vtsc=[0|1] (rdtsc emulation) from
> the vm.cfg file into xen.
> 
> I was using the superpages vm.cfg implementation as a guide,
> but I see the domain builder interface for superpages changed
> in c/s 19963 to pass the value via a flag in a pad byte in
> struct xc_dom_image.  Was this change due to some backward
> compatibility reason?  This looks like a nicer interface,
> but is there another pad byte I can/should use?  If not,
> what's the best way then to pass the vtsc value from the
> tools to Xen?
> 
> Also, will I be able to use the same interface for both
> HVM and PV, or should I use the HVM param interface for
> HVM domains (using the HPET parameter as a model)?
> 
> Thanks,
> Dan
>

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

<Prev in Thread] Current Thread [Next in Thread>