All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gerd Hoffmann <kraxel@redhat.com>,
	Gonglei <arei.gonglei@huawei.com>, Weidong Huang <hwd@huawei.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	peter.huangpeng@huawei.com
Subject: Re: [Qemu-devel] IO port 0x61 is multiple used
Date: Thu, 19 Mar 2015 13:06:44 +0100	[thread overview]
Message-ID: <550ABBD4.6050309@siemens.com> (raw)
In-Reply-To: <1426765305.18873.44.camel@nilsson.home.kraxel.org>

On 2015-03-19 12:41, Gerd Hoffmann wrote:
> On Di, 2015-03-17 at 15:11 +0800, Gonglei wrote:
>> On 2015/3/15 20:49, Weidong Huang wrote:
>>> Hi ALL:
>>>
>>> IO port 0x61 is used by pc speaker and NMI reason port.
>>>
>>> This is ambiguous. How to distinguish in QEMU?

That register is a mess functionality-wise because it serves multiple
hardware units that are at least logically separated - legacy. In QEMU,
the speaker emulation adopted it as it is the only unit that actually
has some functionality behind the bits (see below).

>>>
>>> I see that NMI reason port is not realized in QEMU.
>>>
>>> But linux guest will access this port to determine what the NMI reason code means.
>>>
>>> It will access pc speaker's io port. Is this a bug?
>>>
>> Gerd, any thoughts?
> 
> Not my area of expertise, but can qemu send NMIs to the guest in the
> first place?

QEMU doesn't generate the kind of NMI events that would normally be
reported via the status bits in port 0x61. Therefore, bits 6 and 7 will
always remain unset for now.

Jan

PS: The port name shown in "info mtree" is wrong. Will send a trivial
fix to help identifying the device model behind it.

-- 
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux

      reply	other threads:[~2015-03-19 12:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-15 12:49 [Qemu-devel] IO port 0x61 is multiple used Weidong Huang
2015-03-17  7:11 ` Gonglei
2015-03-19 11:41   ` Gerd Hoffmann
2015-03-19 12:06     ` Jan Kiszka [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=550ABBD4.6050309@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=arei.gonglei@huawei.com \
    --cc=hwd@huawei.com \
    --cc=kraxel@redhat.com \
    --cc=peter.huangpeng@huawei.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.