From: Bing Fan <hptsfb@gmail.com>
To: Anup Patel <apatel@ventanamicro.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Atish Patra <atishp@atishpatra.org>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Andrew Jones <ajones@ventanamicro.com>,
Anup Patel <anup@brainfault.org>,
kvm@vger.kernel.org, kvm-riscv@lists.infradead.org,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] KVM RISC-V APLIC fixes
Date: Fri, 22 Mar 2024 19:35:49 +0800 [thread overview]
Message-ID: <f44de7d9-e03d-483d-96d3-76c63158061d@gmail.com> (raw)
In-Reply-To: <20240321085041.1955293-1-apatel@ventanamicro.com>
Hi,
As you mentioned as below, riscv's aia patch in
https://github.com/avpatel/linux.git
Why is this series of patches not merged into upstream?
在 2024/3/21 16:50, Anup Patel 写道:
> Few fixes for KVM RISC-V in-kernel APLIC emulation which were discovered
> during Linux AIA driver patch reviews.
>
> These patches can also be found in the riscv_kvm_aplic_fixes_v1
> branch at: https://github.com/avpatel/linux.git
>
> Anup Patel (2):
> RISC-V: KVM: Fix APLIC setipnum_le/be write emulation
> RISC-V: KVM: Fix APLIC in_clrip[x] read emulation
>
> arch/riscv/kvm/aia_aplic.c | 37 +++++++++++++++++++++++++++++++------
> 1 file changed, 31 insertions(+), 6 deletions(-)
>
next prev parent reply other threads:[~2024-03-22 11:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 8:50 [PATCH 0/2] KVM RISC-V APLIC fixes Anup Patel
2024-03-21 8:50 ` [PATCH 1/2] RISC-V: KVM: Fix APLIC setipnum_le/be write emulation Anup Patel
2024-03-21 8:50 ` [PATCH 2/2] RISC-V: KVM: Fix APLIC in_clrip[x] read emulation Anup Patel
2024-03-22 11:35 ` Bing Fan [this message]
2024-03-22 11:50 ` [PATCH 0/2] KVM RISC-V APLIC fixes Anup Patel
2024-03-26 4:07 ` Anup Patel
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=f44de7d9-e03d-483d-96d3-76c63158061d@gmail.com \
--to=hptsfb@gmail.com \
--cc=ajones@ventanamicro.com \
--cc=anup@brainfault.org \
--cc=apatel@ventanamicro.com \
--cc=atishp@atishpatra.org \
--cc=kvm-riscv@lists.infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=pbonzini@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox