kvm-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Anup Patel <apatel@ventanamicro.com>
To: Anup Patel <anup@brainfault.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	 Paul Walmsley <pjw@kernel.org>,
	Andrew Jones <ajones@ventanamicro.com>,
	 Atish Patra <atish.patra@linux.dev>,
	 "open list:KERNEL VIRTUAL MACHINE FOR RISC-V (KVM/riscv)"
	<kvm-riscv@lists.infradead.org>,
	KVM General <kvm@vger.kernel.org>,
	 linux-riscv <linux-riscv@lists.infradead.org>
Subject: Re: [GIT PULL] KVM/riscv fixes for 6.18 take #1
Date: Fri, 24 Oct 2025 21:16:45 +0530	[thread overview]
Message-ID: <CAK9=C2VXQRGFChGB2xzkRCzf_GbH2VexjAjO2d83e_tSwhddcw@mail.gmail.com> (raw)
In-Reply-To: <CAAhSdy0h=PuKTG=aWou_8y8qb7kSHS46TLXoXrjrTXN1xv-uQg@mail.gmail.com>

Hi Paolo,

On Fri, Oct 24, 2025 at 4:39 PM Anup Patel <anup@brainfault.org> wrote:
>
> Hi Paolo,
>
> We have three fixes for the 6.18 kernel. Two of these
> are related to checking pending interrupts whereas
> the third one removes automatic I/O mapping from
> kvm_arch_prepare_memory_region().
>
> Please pull.

Please disregard this PR. I will send v2 PR with a build warning fix.

Apologies for the noise.

Regards,
Anup

>
> Regards,
> Anup
>
> The following changes since commit 3a8660878839faadb4f1a6dd72c3179c1df56787:
>
>   Linux 6.18-rc1 (2025-10-12 13:42:36 -0700)
>
> are available in the Git repository at:
>
>   https://github.com/kvm-riscv/linux.git tags/kvm-riscv-fixes-6.18-1
>
> for you to fetch changes up to be01d4d5c30114e9df37fca9efbb2c5cb0ad36f6:
>
>   RISC-V: KVM: Remove automatic I/O mapping for VM_PFNMAP (2025-10-24
> 11:00:48 +0530)
>
> ----------------------------------------------------------------
> KVM/riscv fixes for 6.18, take #1
>
> - Fix check for local interrupts on riscv32
> - Read HGEIP CSR on the correct cpu when checking for IMSIC interrupts
> - Remove automatic I/O mapping from kvm_arch_prepare_memory_region()
>
> ----------------------------------------------------------------
> Fangyu Yu (2):
>       RISC-V: KVM: Read HGEIP CSR on the correct cpu
>       RISC-V: KVM: Remove automatic I/O mapping for VM_PFNMAP
>
> Samuel Holland (1):
>       RISC-V: KVM: Fix check for local interrupts on riscv32
>
>  arch/riscv/kvm/aia_imsic.c | 16 ++++++++++++++--
>  arch/riscv/kvm/mmu.c       | 20 +-------------------
>  arch/riscv/kvm/vcpu.c      |  2 +-
>  3 files changed, 16 insertions(+), 22 deletions(-)
>
> --
> kvm-riscv mailing list
> kvm-riscv@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kvm-riscv

-- 
kvm-riscv mailing list
kvm-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kvm-riscv

      reply	other threads:[~2025-10-24 15:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-24 11:09 [GIT PULL] KVM/riscv fixes for 6.18 take #1 Anup Patel
2025-10-24 15:46 ` Anup Patel [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='CAK9=C2VXQRGFChGB2xzkRCzf_GbH2VexjAjO2d83e_tSwhddcw@mail.gmail.com' \
    --to=apatel@ventanamicro.com \
    --cc=ajones@ventanamicro.com \
    --cc=anup@brainfault.org \
    --cc=atish.patra@linux.dev \
    --cc=kvm-riscv@lists.infradead.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=pbonzini@redhat.com \
    --cc=pjw@kernel.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;
as well as URLs for NNTP newsgroup(s).