All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clg@redhat.com>
To: Wencheng Yang <east.moutain.yang@gmail.com>,
	Alex Williamson <alex@shazbot.org>,
	"Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>,
	"Peter Xu" <peterx@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@mailo.com>,
	Yangwencheng <yangwencheng@gmail.com>
Subject: Re: [PATCH] hw/vfio: Coalesce repeated PCI_COMMAND memory-decode DMA (re)map for passthrough BARs
Date: Thu, 23 Jul 2026 16:55:32 +0200	[thread overview]
Message-ID: <472bf0d9-eb2f-4f42-92ff-968cbae0c6d2@redhat.com> (raw)
In-Reply-To: <CALrP2iVpdgxARSOtCOAj54tiy_+YrNBTu_DS=e_5HVGfC_-ffg@mail.gmail.com>

> Applying the two patches above might help reduce this time. I'm currently
> running QEMU 8.2 with kernel 5.10, and directly cherry-picking these two
> patches resultsin conflicts. I'll spend some time backporting them and
> see how the results look.

Oh. It might be very difficult to do the backport on such
an old code base specially for Linux. And there is more to
it as Alex said.

We would be interested by the results with upstream though.
Could please you give it a try first ? Then, I would rebase
if possible.

Thanks,

C.



      parent reply	other threads:[~2026-07-23 14:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 13:06 [PATCH] hw/vfio: Coalesce repeated PCI_COMMAND memory-decode DMA (re)map for passthrough BARs Yang Wencheng
2026-07-21 14:41 ` Alex Williamson
2026-07-21 15:03   ` Michael S. Tsirkin
2026-07-22  5:00     ` Alex Williamson
2026-07-23  3:50       ` Wencheng Yang
2026-07-23  7:37         ` Cédric Le Goater
2026-07-23 13:44           ` Wencheng Yang
2026-07-23 14:12             ` Alex Williamson
2026-07-23 14:55             ` Cédric Le Goater [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=472bf0d9-eb2f-4f42-92ff-968cbae0c6d2@redhat.com \
    --to=clg@redhat.com \
    --cc=alex@shazbot.org \
    --cc=east.moutain.yang@gmail.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=philmd@mailo.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yangwencheng@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.