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

[PATCH for-4.18 0/5] xenalyze: Miscellaneous fixes

To: xen-devel@xxxxxxxxxxxxxxxxxxxx
From: George Dunlap <george.dunlap@xxxxxxxxx>
Date: Mon, 9 Oct 2023 13:51:32 +0100
Cc: Olaf Hering <olaf@xxxxxxxxx>, Henry Wang <Henry.Wang@xxxxxxx>
Delivery-date: Mon, 09 Oct 2023 12:51:54 +0000
List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

None of these are critical; but they're also in a fairly low
criticality part of the code.  I'd be fine with either putting them in
now or waiting until 4.19.

Follow-Ups:
- Re: [PATCH for-4.18 0/5] xenalyze: Miscellaneous fixes
  - From: Henry Wang
- [PATCH for-4.18 3/5] xenalyze: Don't expect an HVM_HANDLER trace for PAUSE vmexits
  - From: George Dunlap
- [PATCH for-4.18 2/5] xenalyze: AMD's VMEXIT_VINTR doesn't need a trace record
  - From: George Dunlap
- [PATCH for-4.18 4/5] xenalyze: Fix interrupt EIP reporting
  - From: George Dunlap
- [PATCH for-4.18 5/5] xenalyze: Reduce warnings about leaving a vcpu in INIT
  - From: George Dunlap
- [PATCH for-4.18 1/5] xenalyze: Only accumulate data from one vmexit without a handler
  - From: George Dunlap

Prev by Date: [xen-unstable test] 183323: tolerable FAIL
Next by Date: [PATCH for-4.18 1/5] xenalyze: Only accumulate data from one vmexit without a handler
Previous by thread: [xen-unstable test] 183323: tolerable FAIL
Next by thread: [PATCH for-4.18 1/5] xenalyze: Only accumulate data from one vmexit without a handler
Index(es):
- Date
- Thread

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