From: DuanZhenzhong <zhenzhong.duan@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Feng Jin <joe.jin@oracle.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] Bypass mask bit of msix entry in xen
Date: Tue, 26 Mar 2013 11:15:29 +0800 [thread overview]
Message-ID: <515112D1.6020809@oracle.com> (raw)
In-Reply-To: <514B14D002000078000C7801@nat28.tlf.novell.com>
Jan Beulich wrote:
>>>> On 21.03.13 at 11:50, Zhenzhong Duan <zhenzhong.duan@oracle.com> wrote:
>>>>
>> On 2013-03-21 18:12, Jan Beulich wrote:
>>
>>> Furthermore, without explanation I also don't see how the mask
>>> bit is now being dealt with properly: From an abstract pov you'd
>>> need to merge ("or") the guest-requested mask bit state with what
>>> Xen needs for its own purposes. I don't see anything like that here
>>> or in the qemu side patch.
>>>
>> Right, I didn't consider combine xen's masking with guest's.
>> My patch just target making irq affinity in old hvm guest work and
>> sometimes no irq handler panic.
>> But I would like to know what's the result if guest's mask setting
>> doesn't pass to device,
>> interrupt loss or something else? I see current implemention didn't
>> passthrough mask bit too.
>>
>
> The effect of this is unknown, as it depends on the particular
> driver behavior and assumptions. Loss of interrupts, however,
> doesn't appear to be problematic here; instead, interrupts
> getting delivered when the driver doesn't expect them seems
> to be the much bigger problem.
>
> Jan
>
>
It's hard to merge guest requested mask with xen's.
Because xen lack a irq_desc.depth as kernel for nested irq disable and
enable.
--
Regards
zhenzhong
--
Oracle Building, No.24 Building, Zhongguancun Software Park
Haidian District, Beijing 100193, China
prev parent reply other threads:[~2013-03-26 3:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 3:38 [PATCH] Bypass mask bit of msix entry in xen Zhenzhong Duan
2013-03-21 10:12 ` Jan Beulich
2013-03-21 10:50 ` Zhenzhong Duan
2013-03-21 13:10 ` Jan Beulich
2013-03-26 3:15 ` DuanZhenzhong [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=515112D1.6020809@oracle.com \
--to=zhenzhong.duan@oracle.com \
--cc=JBeulich@suse.com \
--cc=joe.jin@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=xen-devel@lists.xen.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 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).