From: Alexander Graf <agraf@suse.de>
To: Paul Janzen <pcj@pauljanzen.org>
Cc: Scott Wood <scottwood@freescale.com>,
"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
qemu-devel <qemu-devel@nongnu.org>,
kvm-ppc <kvm-ppc@vger.kernel.org>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH] openpic: Initialize destmask at reset
Date: Thu, 22 May 2014 12:15:35 +0200 [thread overview]
Message-ID: <537DCE47.2010204@suse.de> (raw)
In-Reply-To: <859BC03D-7C6A-434B-87D3-7A51615970FC@suse.de>
On 21.05.14 21:47, Alexander Graf wrote:
>
>> Am 21.05.2014 um 18:33 schrieb Paul Janzen <pcj@pauljanzen.org>:
>>
>>> On Wed, May 21, 2014 at 12:45 AM, Alexander Graf <agraf@suse.de> wrote:
>>>
>>> Or maybe it's safer overall to just call write_IRQreg_idr() instead of
>>> setting idr directly? That would update destmask along the way as well and
>>> we would catch all subtle corner cases.
>> I considered this initially but decided to go with the simpler
>> approach. But you have convinced me. Specifically, the current
>> implementation does not reset src->output or src->nomask, which
>> write_IRQreg_idr() will. I will test this change and re-submit the
>> patch.
>>
>>> Do you have a simple test case for this patch? We seem to have the same bug
>>> in the in-kernel KVM MPIC emulation code and I'd like to have it fixed there
>>> as well, but I don't really like to do that change blindly.
>> I have tested this patch using a proprietary embedded operating system
>> which doesn't bother to initialize the IDR registers.
> Do you think it'd be possible for you to test whether it works with kvm when I give you a patch? Do you have real hardware to run kvm on? :)
I just checked - we don't properly implement reset at all in the
in-kernel MPIC we do in KVM. So it's merely something to keep in mind
for now until someone sits down and implements proper reset support ;).
Alex
parent reply other threads:[~2014-05-22 10:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <859BC03D-7C6A-434B-87D3-7A51615970FC@suse.de>]
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=537DCE47.2010204@suse.de \
--to=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=pcj@pauljanzen.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=scottwood@freescale.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).