From: Alexander Graf <agraf@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Gabriel Somlo <gsomlo@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] e1000: Delay LSC until mask is active
Date: Thu, 03 Jul 2014 20:00:04 +0200 [thread overview]
Message-ID: <53B59A24.5090000@suse.de> (raw)
In-Reply-To: <CAFEAcA-SvYH1Sd96g4=37Vf=Yh4bpmiaoyET963+OKBFvEjp0w@mail.gmail.com>
On 03.07.14 19:57, Peter Maydell wrote:
> On 3 July 2014 18:39, Alexander Graf <agraf@suse.de> wrote:
>> Mac OS X reads ICR on every interrupt. When the IRQ line is shared, this may
>> result in a race where LSC is not interpreted yet, but already gets cleared.
>>
>> The guest already has a way of telling us that it can interpret LSC events
>> though and that's via the interrupt mask register (IMS).
>>
>> So if we just leave the LSC interrupt bit pending, but invisible to the guest
>> as long as it's not ready to receive LSC interrupts, we basically defer the
>> interrupt to the earliest point in time when the guest would know how to
>> handle it.
> This would break any guests dealing with this in a polling
> mode (ie "permanently leave interrupts masked and read
> ICR periodically to find out whether anything interesting
> has happened"), right?
If those guests would wait for a link detect event that way, yes.
Considering all the hackery we already have about link negotiation
(delay it until a random amount of ms passed) I'd say the breakage this
patch fixes is a lot more likely than a polling guest that waits for a
link based on ICR.LSC :).
Alex
next prev parent reply other threads:[~2014-07-03 18:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 17:39 [Qemu-devel] [PATCH] e1000: Delay LSC until mask is active Alexander Graf
2014-07-03 17:57 ` Peter Maydell
2014-07-03 18:00 ` Alexander Graf [this message]
2014-07-03 20:18 ` Michael S. Tsirkin
2014-07-28 14:07 ` Alexander Graf
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=53B59A24.5090000@suse.de \
--to=agraf@suse.de \
--cc=gsomlo@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@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;
as well as URLs for NNTP newsgroup(s).