On 2019/10/18 下午6:12, Rafael J. Wysocki wrote:
On Wednesday, October 16, 2019 7:56:17 AM CEST Yin, Fengwei wrote:
Hi David,
On 10/15/2019 7:48 PM, David Laight wrote:
From: Yin Fengwei
Sent: 15 October 2019 09:04
In function acpi_idle_do_entry(), an ioport access is used for dummy
wait to
On 10/18/2019 6:12 PM, Rafael J. Wysocki wrote:
On Wednesday, October 16, 2019 7:56:17 AM CEST Yin, Fengwei wrote:
Hi David,
On 10/15/2019 7:48 PM, David Laight wrote:
From: Yin Fengwei
Sent: 15 October 2019 09:04
In function acpi_idle_do_entry(), an ioport access is used for dummy
wait to
On Wednesday, October 16, 2019 7:56:17 AM CEST Yin, Fengwei wrote:
> Hi David,
>
> On 10/15/2019 7:48 PM, David Laight wrote:
> > From: Yin Fengwei
> >> Sent: 15 October 2019 09:04
> >> In function acpi_idle_do_entry(), an ioport access is used for dummy
> >> wait to guarantee hardware behavior.
Hi David,
On 10/15/2019 7:48 PM, David Laight wrote:
From: Yin Fengwei
Sent: 15 October 2019 09:04
In function acpi_idle_do_entry(), an ioport access is used for dummy
wait to guarantee hardware behavior. But it could trigger unnecessary
vmexit in virtualization environment.
If we run linux
From: Yin Fengwei
> Sent: 15 October 2019 09:04
> In function acpi_idle_do_entry(), an ioport access is used for dummy
> wait to guarantee hardware behavior. But it could trigger unnecessary
> vmexit in virtualization environment.
>
> If we run linux as guest and export all available native C
In function acpi_idle_do_entry(), an ioport access is used for dummy
wait to guarantee hardware behavior. But it could trigger unnecessary
vmexit in virtualization environment.
If we run linux as guest and export all available native C state to
guest, we did see many PM timer access triggered
6 matches
Mail list logo