From: Paolo Bonzini <pbonzini@redhat.com>
To: "Gonglei (Arei)" <arei.gonglei@huawei.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "Huangpeng (Peter)" <peter.huangpeng@huawei.com>,
"kevin@koconnor.net" <kevin@koconnor.net>,
"ehabkost@redhat.com" <ehabkost@redhat.com>,
"rth@twiddle.net" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] rtc: introduce nmi disable bit handler for cmos
Date: Mon, 14 Dec 2015 14:37:30 +0100 [thread overview]
Message-ID: <566EC61A.7090407@redhat.com> (raw)
In-Reply-To: <33183CC9F5247A488A2544077AF19020B02B45BB@SZXEMA503-MBS.china.huawei.com>
On 14/12/2015 14:27, Gonglei (Arei) wrote:
>
>>
>> On 14/12/2015 13:49, Gonglei (Arei) wrote:
>>>>>>> This patch introduce nmi disable bit handler to fix the problem
>>>>>>> and make the emulated CMOS like the real hardware.
>>>>>
>>>>> I think that this only works with -machine kernel_irqchip=off, however.
>>> IIRCC, the kernel_irqchip is disabled by default, and we used the default
>> value.
>>
>> No, it's enabled by default.
>>
>
> Okay, yes, I saw the source code again. That means kmod finish the NMI injection
> wrok, and the NMI will not pass Qemu side. So, you thought this patch cannot block
> NMI injection when kernel_irqchip=on ?
I am not sure. It depends on which NMIs are blocked by the bit. For
example, the IOAPIC can deliver NMIs, and they wouldn't be blocked.
Do you have any documentation, to see whether they can actually happen
on emulated hardware? I guess we support the TCO watchdog, so yes.
> Maybe we should pass the nmi_disable bit to Kmod when kernel_irqchip=on , right?
Yes, that's the idea.
But first of all, I've read the thread you linked, and I couldn't find
the place where it says that the root cause is NMIs.
Paolo
next prev parent reply other threads:[~2015-12-14 13:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-12 13:15 [Qemu-devel] [PATCH] rtc: introduce nmi disable bit handler for cmos Gonglei
2015-12-14 9:56 ` Paolo Bonzini
2015-12-14 12:49 ` Gonglei (Arei)
2015-12-14 12:51 ` Paolo Bonzini
2015-12-14 13:27 ` Gonglei (Arei)
2015-12-14 13:37 ` Paolo Bonzini [this message]
2015-12-15 0:58 ` Gonglei (Arei)
2015-12-15 9:34 ` Gonglei (Arei)
2015-12-15 10:43 ` Paolo Bonzini
2015-12-15 18:53 ` Radim Krcmar
2015-12-16 8:26 ` Gonglei (Arei)
2015-12-16 8:51 ` Paolo Bonzini
2015-12-16 10:28 ` Gonglei (Arei)
2015-12-16 12:14 ` Paolo Bonzini
2015-12-17 7:17 ` Gonglei (Arei)
2015-12-17 8:37 ` Paolo Bonzini
2015-12-17 9:04 ` Gonglei (Arei)
2015-12-14 18:16 ` Eduardo Habkost
2015-12-15 1:00 ` Gonglei (Arei)
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=566EC61A.7090407@redhat.com \
--to=pbonzini@redhat.com \
--cc=arei.gonglei@huawei.com \
--cc=ehabkost@redhat.com \
--cc=kevin@koconnor.net \
--cc=peter.huangpeng@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).