On Mon, Mar 24, 2025 at 05:30:49PM +, Mingwei Zhang wrote:
> From: Kan Liang
>
> When entering/exiting a guest, some contexts for a guest have to be
> switched. For examples, there is a dedicated interrupt vector for
> guests on Intel platforms.
>
> When PMI switch into a new guest vector, g
On 5/15/2025 7:30 AM, Sean Christopherson wrote:
> On Mon, Mar 24, 2025, Mingwei Zhang wrote:
>> From: Kan Liang
>>
>> When entering/exiting a guest, some contexts for a guest have to be
>> switched. For examples, there is a dedicated interrupt vector for
>> guests on Intel platforms.
>>
>> When
On Mon, Mar 24, 2025, Mingwei Zhang wrote:
> From: Kan Liang
>
> When entering/exiting a guest, some contexts for a guest have to be
> switched. For examples, there is a dedicated interrupt vector for
> guests on Intel platforms.
>
> When PMI switch into a new guest vector, guest_lvtpc value nee
On Mon, Mar 24, 2025 at 05:30:49PM +, Mingwei Zhang wrote:
> @@ -1822,7 +1835,7 @@ extern int perf_event_period(struct perf_event *event,
> u64 value);
> extern u64 perf_event_pause(struct perf_event *event, bool reset);
> int perf_get_mediated_pmu(void);
> void perf_put_mediated_pmu(void)
From: Kan Liang
When entering/exiting a guest, some contexts for a guest have to be
switched. For examples, there is a dedicated interrupt vector for
guests on Intel platforms.
When PMI switch into a new guest vector, guest_lvtpc value need to be
reflected onto HW, e,g., guest clear PMI mask bit
5 matches
Mail list logo