From: Michael Tokarev <mjt@tls.msk.ru>
To: Li Zhijian <lizhijian@fujitsu.com>, qemu-devel@nongnu.org
Cc: linux-cxl@vger.kernel.org,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Fan Ni <fan.ni@samsung.com>, qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [PATCH v3] hw/cxl: Fix msix_notify: Assertion `vector < dev->msix_entries_nr`
Date: Fri, 17 Jan 2025 10:20:44 +0300 [thread overview]
Message-ID: <9c06632b-751b-4a2f-aa87-e07691bebfba@tls.msk.ru> (raw)
In-Reply-To: <20250115075834.167504-1-lizhijian@fujitsu.com>
15.01.2025 10:58, Li Zhijian via wrote:
> This assertion always happens when we sanitize the CXL memory device.
> $ echo 1 > /sys/bus/cxl/devices/mem0/security/sanitize
>
> It is incorrect to register an MSIX number beyond the device's capability.
>
> Increase the device's MSIX number to cover the mailbox msix number(9).
This seems to be like a qemu-stable material (8.2+), is it not?
Thanks,
/mjt
> Fixes: 43efb0bfad2b ("hw/cxl/mbox: Wire up interrupts for background completion")
> Signed-off-by: Li Zhijian <lizhijian@fujitsu.com>
> ---
> V3:
> Just increate the device's msix number, A new enumeration will be introduced in later patch. # Jonathan
>
> V2:
> Just increase msix number and add enum to maintainer their values # Jonathan
> ---
> hw/mem/cxl_type3.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/hw/mem/cxl_type3.c b/hw/mem/cxl_type3.c
> index bd7652740f4b..0ae1704a345c 100644
> --- a/hw/mem/cxl_type3.c
> +++ b/hw/mem/cxl_type3.c
> @@ -843,7 +843,7 @@ static void ct3_realize(PCIDevice *pci_dev, Error **errp)
> ComponentRegisters *regs = &cxl_cstate->crb;
> MemoryRegion *mr = ®s->component_registers;
> uint8_t *pci_conf = pci_dev->config;
> - unsigned short msix_num = 6;
> + unsigned short msix_num = 10;
> int i, rc;
> uint16_t count;
>
next prev parent reply other threads:[~2025-01-17 7:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 7:58 [PATCH v3] hw/cxl: Fix msix_notify: Assertion `vector < dev->msix_entries_nr` Li Zhijian
2025-01-15 13:44 ` Jonathan Cameron
2025-01-17 7:20 ` Michael Tokarev [this message]
2025-01-17 11:16 ` Jonathan Cameron
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=9c06632b-751b-4a2f-aa87-e07691bebfba@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=fan.ni@samsung.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=lizhijian@fujitsu.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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