mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bibo Mao <maobibo@loongson.cn>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: Tianrui Zhao <zhaotianrui@loongson.cn>,
	Xianglai Li <lixianglai@loongson.cn>,
	kvm@vger.kernel.org, loongarch@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 00/13] LoongArch: KVM: Enhancement with eiointc emulation
Date: Mon, 7 Jul 2025 11:51:49 +0800	[thread overview]
Message-ID: <f71ceea8-e690-19cc-95a5-3f4ad25b3223@loongson.cn> (raw)
In-Reply-To: <CAAhV-H6pt74LDg0idJ=71RG9MDh2KkMxE-Fao-qCFexyd8fz4A@mail.gmail.com>



On 2025/7/1 下午6:48, Huacai Chen wrote:
> Hi, Bibo,
> 
> On Tue, Jul 1, 2025 at 11:08 AM Bibo Mao <maobibo@loongson.cn> wrote:
>>
>> This series add generic eiointc 8 bytes access interface, so that 1/2/4/8
>> bytes access can use the generic 8 bytes access interface. It reduce
>> about 300 lines redundant code and make eiointc emulation driver simple
>> than ever.
>>
>> ---
>> v4 ... v5
>>    1. Rebase patch on latest kernel where bugfix of eiointc has been
>>       merged.
>>    2. Add generic eiointc 8 bytes access interface, 1/2/4/8 bytes access
>>       uses generic 8 bytes access interface.
>>
>> v3 ... v4:
>>    1. Remove patch about enhancement and only keep bugfix relative
>>       patches.
>>    2. Remove INTC indication in the patch title.
>>    3. With access size, keep default case unchanged besides 1/2/4/8 since
>>       here all patches are bugfix
>>    4. Firstly check return value of copy_from_user() with error path,
>>       keep the same order with old patch in patch 4.
>>
>> v2 ... v3:
>>    1. Add prefix INTC: in title of every patch.
>>    2. Fix array index overflow when emulate register EIOINTC_ENABLE
>>       writing operation.
>>    3. Add address alignment check with eiointc register access operation.
>>
>> v1 ... v2:
>>    1. Add extra fix in patch 3 and patch 4, add num_cpu validation check
>>    2. Name of stat information keeps unchanged, only move it from VM stat
>>       to vCPU stat.
>> ---
>> Bibo Mao (13):
>>    LoongArch: KVM: Use standard bitops API with eiointc
>>    LoongArch: KVM: Remove unused parameter len
>>    LoongArch: KVM: Add stat information with kernel irqchip
>>    LoongArch: KVM: Remove never called default case statement
>>    LoongArch: KVM: Rename loongarch_eiointc_readq with
>>      loongarch_eiointc_read
>>    LoongArch: KVM: Use generic read function loongarch_eiointc_read
>>    LoongArch: KVM: Remove some unnecessary local variables
>>    LoongArch: KVM: Use concise api __ffs()
>>    LoongArch: KVM: Replace eiointc_enable_irq() with eiointc_update_irq()
>>    LoongArch: KVM: Remove local variable offset
>>    LoongArch: KVM: Rename old_data with old
>>    LoongArch: KVM: Add generic function loongarch_eiointc_write()
>>    LoongArch: KVM: Use generic interface loongarch_eiointc_write()
> Patch5 and Patch6 can be squashed, Patch7 and Patch10 can be squashed,
> Patch8 and Patch9 can be squshed, Patch12 and Patch13 can be squashed,
> Patch11 is useless so can be removed.
Thanks for reviewing, will do in this way.

Regards
Bibo Mao
> 
> 
> Huacai
> 
>>
>>   arch/loongarch/include/asm/kvm_host.h |  12 +-
>>   arch/loongarch/kvm/intc/eiointc.c     | 557 ++++----------------------
>>   arch/loongarch/kvm/intc/ipi.c         |  28 +-
>>   arch/loongarch/kvm/intc/pch_pic.c     |   4 +-
>>   arch/loongarch/kvm/vcpu.c             |   8 +-
>>   5 files changed, 102 insertions(+), 507 deletions(-)
>>
>>
>> base-commit: d0b3b7b22dfa1f4b515fd3a295b3fd958f9e81af
>> --
>> 2.39.3
>>


      reply	other threads:[~2025-07-07  3:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-01  3:08 Bibo Mao
2025-07-01  3:08 ` [PATCH v5 01/13] LoongArch: KVM: Use standard bitops API with eiointc Bibo Mao
2025-07-01  3:08 ` [PATCH v5 02/13] LoongArch: KVM: Remove unused parameter len Bibo Mao
2025-07-01  3:08 ` [PATCH v5 03/13] LoongArch: KVM: Add stat information with kernel irqchip Bibo Mao
2025-07-01  3:08 ` [PATCH v5 04/13] LoongArch: KVM: Remove never called default case statement Bibo Mao
2025-07-01  3:08 ` [PATCH v5 05/13] LoongArch: KVM: Rename loongarch_eiointc_readq with loongarch_eiointc_read Bibo Mao
2025-07-01  3:08 ` [PATCH v5 06/13] LoongArch: KVM: Use generic read function loongarch_eiointc_read Bibo Mao
2025-07-01  3:08 ` [PATCH v5 07/13] LoongArch: KVM: Remove some unnecessary local variables Bibo Mao
2025-07-01  3:08 ` [PATCH v5 08/13] LoongArch: KVM: Use concise api __ffs() Bibo Mao
2025-07-01  3:15 ` [PATCH v5 09/13] LoongArch: KVM: Replace eiointc_enable_irq() with eiointc_update_irq() Bibo Mao
2025-07-01  3:15   ` [PATCH v5 10/13] LoongArch: KVM: Remove local variable offset Bibo Mao
2025-07-01  3:15   ` [PATCH v5 11/13] LoongArch: KVM: Rename old_data with old Bibo Mao
2025-07-01  3:15   ` [PATCH v5 12/13] LoongArch: KVM: Add generic function loongarch_eiointc_write() Bibo Mao
2025-07-01  3:15   ` [PATCH v5 13/13] LoongArch: KVM: Use generic interface loongarch_eiointc_write() Bibo Mao
2025-07-01 10:48 ` [PATCH v5 00/13] LoongArch: KVM: Enhancement with eiointc emulation Huacai Chen
2025-07-07  3:51   ` Bibo Mao [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=f71ceea8-e690-19cc-95a5-3f4ad25b3223@loongson.cn \
    --to=maobibo@loongson.cn \
    --cc=chenhuacai@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lixianglai@loongson.cn \
    --cc=loongarch@lists.linux.dev \
    --cc=zhaotianrui@loongson.cn \
    /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

all inboxes | Powered by JetHome®