On 24.07.2025 05:42, dm...@proton.me wrote:
> On Thu, Jul 24, 2025 at 03:00:46AM +0000, dm...@proton.me wrote:
>> On Wed, Jul 23, 2025 at 12:37:41PM -0400, Stewart Hildebrand wrote:
>>> Introduce vPCI BAR mapping task queue. Decouple map operation state from
>>> general vPCI state: in particular, move the per-BAR rangeset out of
>>> struct vpci and into the map task struct.
>>>
>>> This is preparatory work for further changes that need to perform
>>> multiple unmap/map operations before returning to guest.
>>>
>>> Signed-off-by: Stewart Hildebrand <stewart.hildebr...@amd.com>
>>> ---
>>> v1->v2:
>>> * new patch
>>>
>>> Related: 622bdd962822 ("vpci/header: handle p2m range sets per BAR")
>>> ---
>>> xen/common/domain.c | 4 +
>>> xen/drivers/vpci/header.c | 197 +++++++++++++++++++++++---------------
>>> xen/drivers/vpci/vpci.c | 3 -
>>> xen/include/xen/vpci.h | 16 +++-
>>> 4 files changed, 139 insertions(+), 81 deletions(-)
Why did I (and many others) end up on the To: list of this reply? (Breaks my
rules of sorting incoming mail into appropriate folders, for context.) Also,
please trim reply context suitably. Without you doing so, every single reader
will need to scroll through the entirety of a long mail just to find (in this
case) a single line of reply (somewhere in the middle). Of course you
shouldn't be too agressive with trimming, to retain proper context for your
reply.
Jan
