On Mon, Aug 05, 2013 at 08:20:53AM -0700, H. Peter Anvin wrote:
> On 08/05/2013 07:34 AM, Konrad Rzeszutek Wilk wrote:
> >
> > Could you provide me with a git branch so I can test it overnight please?
> >
>
> Pull tip:x86/paravirt.
It works for me. Thanks.
>
> -hpa
>
>
--
To
On 08/05/2013 07:34 AM, Konrad Rzeszutek Wilk wrote:
>
> Could you provide me with a git branch so I can test it overnight please?
>
Pull tip:x86/paravirt.
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Mon, Aug 05, 2013 at 11:38:14AM +0800, Jason Wang wrote:
> On 07/25/2013 04:54 PM, Jason Wang wrote:
> > We try to handle the hypervisor compatibility mode by detecting hypervisor
> > through a specific order. This is not robust, since hypervisors may
> > implement
> > each others features.
>
On Mon, Aug 05, 2013 at 11:38:14AM +0800, Jason Wang wrote:
On 07/25/2013 04:54 PM, Jason Wang wrote:
We try to handle the hypervisor compatibility mode by detecting hypervisor
through a specific order. This is not robust, since hypervisors may
implement
each others features.
This
On 08/05/2013 07:34 AM, Konrad Rzeszutek Wilk wrote:
Could you provide me with a git branch so I can test it overnight please?
Pull tip:x86/paravirt.
-hpa
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
On Mon, Aug 05, 2013 at 08:20:53AM -0700, H. Peter Anvin wrote:
On 08/05/2013 07:34 AM, Konrad Rzeszutek Wilk wrote:
Could you provide me with a git branch so I can test it overnight please?
Pull tip:x86/paravirt.
It works for me. Thanks.
-hpa
--
To unsubscribe from this
On 07/25/2013 04:54 PM, Jason Wang wrote:
> We try to handle the hypervisor compatibility mode by detecting hypervisor
> through a specific order. This is not robust, since hypervisors may implement
> each others features.
>
> This patch tries to handle this situation by always choosing the last
On 07/25/2013 04:54 PM, Jason Wang wrote:
We try to handle the hypervisor compatibility mode by detecting hypervisor
through a specific order. This is not robust, since hypervisors may implement
each others features.
This patch tries to handle this situation by always choosing the last one in
linux-foundation.org
> Subject: [PATCH V2 4/4] x86: correctly detect hypervisor
>
> We try to handle the hypervisor compatibility mode by detecting hypervisor
> through a specific order. This is not robust, since hypervisors may implement
> each others features.
>
> This patc
We try to handle the hypervisor compatibility mode by detecting hypervisor
through a specific order. This is not robust, since hypervisors may implement
each others features.
This patch tries to handle this situation by always choosing the last one in the
CPUID leaves. This is done by letting
We try to handle the hypervisor compatibility mode by detecting hypervisor
through a specific order. This is not robust, since hypervisors may implement
each others features.
This patch tries to handle this situation by always choosing the last one in the
CPUID leaves. This is done by letting
] x86: correctly detect hypervisor
We try to handle the hypervisor compatibility mode by detecting hypervisor
through a specific order. This is not robust, since hypervisors may implement
each others features.
This patch tries to handle this situation by always choosing the last one
12 matches
Mail list logo
