From: Jason Wang <jasowang@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>,
Dmitry Fleytman <dmitry.fleytman@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2] e1000e: Prevent MSI/MSI-X storms
Date: Mon, 2 Jul 2018 11:40:37 +0800 [thread overview]
Message-ID: <a5f14cd7-1334-e3f8-c3c8-e40443351372@redhat.com> (raw)
In-Reply-To: <6b6e45bf-362f-1305-6991-69749d5f02f9@web.de>
On 2018年06月30日 14:13, Jan Kiszka wrote:
> On 2018-04-05 19:41, Jan Kiszka wrote:
>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> Only signal MSI/MSI-X events on rising edges. So far we re-triggered the
>> interrupt sources even if the guest did no consumed the pending one,
>> easily causing interrupt storms.
>>
>> Issue was observable with Linux 4.16 e1000e driver when MSI-X was used.
>> Vector 2 was causing interrupt storms after the driver activated the
>> device.
>>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>> ---
>>
>> Changes in v2:
>> - also update msi_causes_pending after EIAC changes (required because
>> there is no e1000e_update_interrupt_state after that
>>
>> hw/net/e1000e_core.c | 11 +++++++++++
>> hw/net/e1000e_core.h | 2 ++
>> 2 files changed, 13 insertions(+)
>>
>> diff --git a/hw/net/e1000e_core.c b/hw/net/e1000e_core.c
>> index c93c4661ed..d6ddd59986 100644
>> --- a/hw/net/e1000e_core.c
>> +++ b/hw/net/e1000e_core.c
>> @@ -2027,6 +2027,7 @@ e1000e_msix_notify_one(E1000ECore *core, uint32_t cause, uint32_t int_cfg)
>> }
>>
>> core->mac[ICR] &= ~effective_eiac;
>> + core->msi_causes_pending &= ~effective_eiac;
>>
>> if (!(core->mac[CTRL_EXT] & E1000_CTRL_EXT_IAME)) {
>> core->mac[IMS] &= ~effective_eiac;
>> @@ -2123,6 +2124,13 @@ e1000e_send_msi(E1000ECore *core, bool msix)
>> {
>> uint32_t causes = core->mac[ICR] & core->mac[IMS] & ~E1000_ICR_ASSERTED;
>>
>> + core->msi_causes_pending &= causes;
>> + causes ^= core->msi_causes_pending;
>> + if (causes == 0) {
>> + return;
>> + }
>> + core->msi_causes_pending |= causes;
>> +
>> if (msix) {
>> e1000e_msix_notify(core, causes);
>> } else {
>> @@ -2160,6 +2168,9 @@ e1000e_update_interrupt_state(E1000ECore *core)
>> core->mac[ICS] = core->mac[ICR];
>>
>> interrupts_pending = (core->mac[IMS] & core->mac[ICR]) ? true : false;
>> + if (!interrupts_pending) {
>> + core->msi_causes_pending = 0;
>> + }
>>
>> trace_e1000e_irq_pending_interrupts(core->mac[ICR] & core->mac[IMS],
>> core->mac[ICR], core->mac[IMS]);
>> diff --git a/hw/net/e1000e_core.h b/hw/net/e1000e_core.h
>> index 7d8ff41890..63a15510cc 100644
>> --- a/hw/net/e1000e_core.h
>> +++ b/hw/net/e1000e_core.h
>> @@ -109,6 +109,8 @@ struct E1000Core {
>> NICState *owner_nic;
>> PCIDevice *owner;
>> void (*owner_start_recv)(PCIDevice *d);
>> +
>> + uint32_t msi_causes_pending;
>> };
>>
>> void
>>
> Ping again, this one is still open.
>
> Jan
Sorry for the late.
Just one thing to confirm, I think the reason that we don't need to
migrate msi_cause_pending is that it can only lead at most one more
signal of MSI on destination?
Thanks
next prev parent reply other threads:[~2018-07-02 3:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 17:41 [Qemu-devel] [PATCH v2] e1000e: Prevent MSI/MSI-X storms Jan Kiszka
2018-06-30 6:13 ` Jan Kiszka
2018-07-02 3:40 ` Jason Wang [this message]
2018-07-02 5:14 ` Jan Kiszka
2018-07-03 4:01 ` Jason Wang
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=a5f14cd7-1334-e3f8-c3c8-e40443351372@redhat.com \
--to=jasowang@redhat.com \
--cc=dmitry.fleytman@gmail.com \
--cc=jan.kiszka@web.de \
--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;
as well as URLs for NNTP newsgroup(s).