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-ia64-devel

RE: [Xen-ia64-devel] RE: PATCH: PAL_VM_SUMMARY and PAL_VM_INFO

To: "Yang, Fred" <fred.yang@xxxxxxxxx>, "Williamson, Alex (Linux Kernel Dev)" <alex.williamson@xxxxxx>
Subject: RE: [Xen-ia64-devel] RE: PATCH: PAL_VM_SUMMARY and PAL_VM_INFO
From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
Date: Thu, 6 Apr 2006 14:17:59 -0700
Cc: Tristan Gingold <Tristan.Gingold@xxxxxxxx>, xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 06 Apr 2006 14:18:15 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcZZtYUJIsBye+zsTgqktb4WFrDKswAApNDQAAFtoWAAAEVBwA==
Thread-topic: [Xen-ia64-devel] RE: PATCH: PAL_VM_SUMMARY and PAL_VM_INFO
I agree completely.  The right answer is for non-VTI Xen/ia64
to eventually support PKRs.  So this is just a discussion
about what to report now from PAL.  Reporting 16 is a lie
and reporting 0 is architecturally incorrect.

I suppose the the answer (0 or 16) is unlikely to matter
anytime soon so I withdraw that objection to Tristan's patch.

Dan

> Wondering if there will be yet another OS got 
> para-virtualized to run on
> Xen/IPF.   Though supporting para-virtualized OS, we should 
> continue to
> maintain a "complete" and "minimal" architectural instead of creating
> yet another legacy architecture.  Or a new driver in XenLinux to take
> advantage of this pkrs.
> 
> 16pkrs would be necessary for architectural completeness.
> 
> -Fred
> 
> -----Original Message-----
> From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> Magenheimer, Dan (HP Labs Fort Collins)
> Sent: Thursday, April 06, 2006 1:26 PM
> To: Williamson, Alex (Linux Kernel Dev)
> Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx; Tristan Gingold
> Subject: [Xen-ia64-devel] RE: PATCH: PAL_VM_SUMMARY and PAL_VM_INFO
> 
> > From: Williamson, Alex (Linux Kernel Dev) 
> > Sent: Thursday, April 06, 2006 2:06 PM
> > To: Magenheimer, Dan (HP Labs Fort Collins)
> > Cc: Tristan Gingold; xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> > Subject: RE: PATCH: PAL_VM_SUMMARY and PAL_VM_INFO
> > 
> > On Thu, 2006-04-06 at 09:30 -0700, Magenheimer, Dan (HP Labs Fort
> > Collins) wrote:
> > 
> > > max_pkr should probably be zero for now (at least non-VT) since
> > > pkr's are not implemented.  Or would this be an "illegal" value
> > > because of architectural definition.
> > 
> >   Looks like that could be considered illegal, the SDM says 
> > there are at
> > least 16 PKRs.
> 
> Given that PKRs are currently unimplemented, returning
> an illegal value (0) might be the right thing anyway.
> 
> Dan
> 
> _______________________________________________
> Xen-ia64-devel mailing list
> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-ia64-devel
> 

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

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