>>> On 22.03.16 at 15:06, wrote:
> On 3/15/16 10:34 AM, Andrew Cooper wrote:
>> None of these features are interesting for Xen to use, or to be advertised
> to
>> guests. Doing so identifies further areas of code which can be removed now
>> that 32bit support has been dropped.
>>
>> IA64 has a
On 3/15/16 10:34 AM, Andrew Cooper wrote:
> None of these features are interesting for Xen to use, or to be advertised to
> guests. Doing so identifies further areas of code which can be removed now
> that 32bit support has been dropped.
>
> IA64 has a sole user in microcode_intel.c. While it is
On 16/03/16 07:53, Konrad Rzeszutek Wilk wrote:
> On Tue, Mar 15, 2016 at 03:34:57PM +, Andrew Cooper wrote:
>> None of these features are interesting for Xen to use, or to be advertised to
>> guests. Doing so identifies further areas of code which can be removed now
>> that 32bit support has
On Tue, Mar 15, 2016 at 03:34:57PM +, Andrew Cooper wrote:
> None of these features are interesting for Xen to use, or to be advertised to
> guests. Doing so identifies further areas of code which can be removed now
> that 32bit support has been dropped.
>
> IA64 has a sole user in microcode_
None of these features are interesting for Xen to use, or to be advertised to
guests. Doing so identifies further areas of code which can be removed now
that 32bit support has been dropped.
IA64 has a sole user in microcode_intel.c. While it is plausible for a 32bit
x86 hypervisor to get there v
