[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH for-4.18 2/5] xenalyze: AMD's VMEXIT_VINTR doesn't need a trace record

To: George Dunlap <george.dunlap@xxxxxxxxx>
From: Anthony PERARD <anthony.perard@xxxxxxxxxx>
Date: Mon, 16 Oct 2023 11:55:32 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxx, Olaf Hering <olaf@xxxxxxxxx>, Henry Wang <Henry.Wang@xxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Xenia Ragiadakou <xenia.ragiadakou@xxxxxxx>, Anthony Perard <anthony.perard@xxxxxxxxx>
Delivery-date: Mon, 16 Oct 2023 10:55:36 +0000
List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On Mon, Oct 09, 2023 at 01:51:34PM +0100, George Dunlap wrote:
> Just like Intel's PENDING_VIRT_INTR, AMD's VINTR doesn't need an HVM
> trace record.  Expect that.
> 
> Signed-off-by: George Dunlap <george.dunlap@xxxxxxxxx>

Acked-by: Anthony PERARD <anthony.perard@xxxxxxxxxx>

Thanks,

-- 
Anthony PERARD

References:
- [PATCH for-4.18 0/5] xenalyze: Miscellaneous fixes
  - From: George Dunlap
- [PATCH for-4.18 2/5] xenalyze: AMD's VMEXIT_VINTR doesn't need a trace record
  - From: George Dunlap

Prev by Date: Re: [PATCH for-4.18 1/5] xenalyze: Only accumulate data from one vmexit without a handler
Next by Date: Re: [PATCH for-4.18 3/5] xenalyze: Don't expect an HVM_HANDLER trace for PAUSE vmexits
Previous by thread: [PATCH for-4.18 2/5] xenalyze: AMD's VMEXIT_VINTR doesn't need a trace record
Next by thread: [PATCH for-4.18 3/5] xenalyze: Don't expect an HVM_HANDLER trace for PAUSE vmexits
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.