From: Bin Guo <guobin@linux.alibaba.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, kvm@vger.kernel.org
Subject: [PATCH 0/2] kvm: minor cleanups in kvm_close and kvm_irqchip_release_virq
Date: Sat, 9 May 2026 10:45:37 +0800 [thread overview]
Message-ID: <20260509024539.90998-1-guobin@linux.alibaba.com> (raw)
Two small cleanups in kvm-all.c:
- Patch 1 removes a redundant null/fd check in kvm_close() that
can never be true once the early-return guard at function entry
has already passed.
- Patch 2 fixes an off-by-one in kvm_irqchip_release_virq(): after
a swap-remove the newly placed entry at the same index was never
re-examined, so a duplicate GSI could be silently left in the
routing table.
Bin Guo (2):
kvm: remove redundant check in kvm_close
kvm: fix kvm_irqchip_release_virq loop after swap-remove
accel/kvm/kvm-all.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
--
2.50.1 (Apple Git-155)
next reply other threads:[~2026-05-09 2:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 2:45 Bin Guo [this message]
2026-05-09 2:45 ` [PATCH 1/2] kvm: remove redundant check in kvm_close Bin Guo
2026-05-09 2:45 ` [PATCH 2/2] kvm: fix kvm_irqchip_release_virq loop after swap-remove Bin Guo
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=20260509024539.90998-1-guobin@linux.alibaba.com \
--to=guobin@linux.alibaba.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox