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/

Home

xen-ppc-devel

[Top] [All Lists]

Re: [XenPPC] [Patch] Detect non hypervisor hardware

from [Mark F Mergen]

[Permanent Link][Original]

To:	hollisb@xxxxxxxxxx
Subject:	Re: [XenPPC] [Patch] Detect non hypervisor hardware
From:	Mark F Mergen <mergen@xxxxxxxxxx>
Date:	Sun, 16 Apr 2006 16:29:35 -0400
Cc:	xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date:	Sun, 16 Apr 2006 13:30:02 -0700
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
Importance:	Normal
In-reply-to:	<1145026480.6003.9.camel@xxxxxxxxxxxxxxxxxxxxx>
List-help:	<mailto:xen-ppc-devel-request@lists.xensource.com?subject=help>
List-id:	Xen PPC development <xen-ppc-devel.lists.xensource.com>
List-post:	<mailto:xen-ppc-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel>, <mailto:xen-ppc-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-ppc-devel-bounces@xxxxxxxxxxxxxxxxxxx
Sensitivity:

The term "problem state" is well-established and well-documented in PowerPC
architecture.  I don't think we need to apologize for using this term in
code specific to PowerPC.  If there is an argument about terminology to be
had, I think we should have it with PowerPC architects, not about code
written to that architecture.

Mark

hollisb@xxxxxxxxxxxxxxxxxxxxxxx@lists.xensource.com on 04/14/2006 10:54:40
AM

Sent by:    xen-ppc-devel-bounces@xxxxxxxxxxxxxxxxxxx


To:    Maria Butrico <butrico@xxxxxxxxxxxxxx>
cc:    xen-ppc-devel@xxxxxxxxxxxxxxxxxxx
Subject:    Re: [XenPPC] [Patch] Detect non hypervisor hardware

...
...
...
"Problem state" is a term that nobody outside PowerPC will understand,
so I would prefer a different name.
...
...
...

--
Hollis Blanchard
IBM Linux Technology Center


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

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
Re: [XenPPC] [Patch] Detect non hypervisor hardware, (continued) Re: [XenPPC] [Patch] Detect non hypervisor hardware, Jimi Xenidis Re: [XenPPC] [Patch] Detect non hypervisor hardware, Hollis Blanchard Re: [XenPPC] [Patch] Detect non hypervisor hardware, Maria Butrico Re: [XenPPC] [Patch] Detect non hypervisor hardware, Hollis Blanchard Re: [XenPPC] [Patch] Detect non hypervisor hardware, Jimi Xenidis Re: [XenPPC] [Patch] Detect non hypervisor hardware, Hollis Blanchard Re: [XenPPC] [Patch] Detect non hypervisor hardware, Jimi Xenidis Re: [XenPPC] [Patch] Detect non hypervisor hardware, Jimi Xenidis Re: [XenPPC] [Patch] Detect non hypervisor hardware, Hollis Blanchard Re: [XenPPC] [Patch] Detect non hypervisor hardware, Maria Butrico Re: [XenPPC] [Patch] Detect non hypervisor hardware, Mark F Mergen <=

Previous by Date:	Re: [XenPPC] [Patch] Detect non hypervisor hardware, Jimi Xenidis
Next by Date:	Re: [XenPPC] [Patch] Detect non hypervisor hardware, Hollis Blanchard
Previous by Thread:	Re: [XenPPC] [Patch] Detect non hypervisor hardware, Maria Butrico
Next by Thread:	[XenPPC] merge and hg troubles, Hollis Blanchard
Indexes:	[Date] [Thread] [Top] [All Lists]

This site is hosted by Citrix