From: Stefan Hajnoczi <stefanha@gmail.com>
To: Luigi Rizzo <rizzo@iet.unipi.it>
Cc: Giuseppe Lettieri <giuseppe.lettieri@iet.unipi.it>,
qemu-devel@nongnu.org, v.maffione@gmail.com
Subject: Re: [Qemu-devel] [RFC] updated e1000 mitigation patch
Date: Thu, 10 Jan 2013 13:25:48 +0100 [thread overview]
Message-ID: <20130110122548.GB30946@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <20121227100658.GB48891@onelab2.iet.unipi.it>
On Thu, Dec 27, 2012 at 11:06:58AM +0100, Luigi Rizzo wrote:
> diff -urp qemu-1.3.0-orig/hw/e1000.c qemu-1.3.0/hw/e1000.c
> --- qemu-1.3.0-orig/hw/e1000.c 2012-12-03 20:37:05.000000000 +0100
> +++ qemu-1.3.0/hw/e1000.c 2012-12-27 09:47:16.000000000 +0100
> @@ -35,6 +35,8 @@
>
> #include "e1000_hw.h"
>
> +static int mit_on = 1; /* interrupt mitigation enable */
If you want to make this optional then please put it inside E1000State
so it can be toggled per NIC.
If you don't want to make it optional then please post results for
recent Linux and Windows guests to show that out-of-the-box performance
is not degraded.
> #define E1000_DEBUG
>
> #ifdef E1000_DEBUG
> @@ -129,6 +131,9 @@ typedef struct E1000State_st {
> } eecd_state;
>
> QEMUTimer *autoneg_timer;
> + QEMUTimer *mit_timer; // handle for the timer
> + uint32_t mit_timer_on; // mitigation timer active
> + uint32_t mit_cause; // pending interrupt cause
Live migration support is required so that pending interrupts are
migrated. We cannot lose interrupts across live migration.
I would migrate mit_cause but not mit_timer_on. When loading (resuming
from live migration), look at mit_cause and raise any interrupts.
Stefan
next prev parent reply other threads:[~2013-01-10 12:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 10:06 [Qemu-devel] [RFC] updated e1000 mitigation patch Luigi Rizzo
2012-12-28 17:48 ` Blue Swirl
2013-01-10 12:25 ` Stefan Hajnoczi [this message]
2013-01-11 14:53 ` [Qemu-devel] nic-specific options ? (Re: [RFC] updated e1000 mitigation patch) Luigi Rizzo
2013-01-14 8:58 ` Stefan Hajnoczi
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=20130110122548.GB30946@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=giuseppe.lettieri@iet.unipi.it \
--cc=qemu-devel@nongnu.org \
--cc=rizzo@iet.unipi.it \
--cc=v.maffione@gmail.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;
as well as URLs for NNTP newsgroup(s).