From: Haitao Shan <maillists.shan@gmail.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: use of struct hvm_irq_dpci in pv guests
Date: Thu, 21 Apr 2011 15:02:49 +0800 [thread overview]
Message-ID: <BANLkTinab3aJwZHFu0qk8J6_faRuaM8UaA@mail.gmail.com> (raw)
In-Reply-To: <4D94904302000078000395FA@vpn.id2.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 789 bytes --]
Hi, Jan,
I think it should be protected by is_hvm_domain(). Anyway, I have saw your
patches already in upstream Xen.
Shan Haitao
2011/3/31 Jan Beulich <JBeulich@novell.com>
> The per-domain pointer to this is stored in ->arch.hvm_domain.irq.dpci,
> hence suggesting that this is a HVM only field.
> do_domctl(XEN_DOMCTL_bind_pt_irq) and domain_get_irq_dpci()
> access it however without considering HVM-ness. In the course of
> splitting/shrinking struct domain, I'd therefore need to know whether
> this field ought to become common, or whether all accessors of the
> field need to get protected by is_hvm_domain().
>
> Thanks, Jan
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
[-- Attachment #1.2: Type: text/html, Size: 1320 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2011-04-21 7:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 12:31 use of struct hvm_irq_dpci in pv guests Jan Beulich
2011-04-21 7:02 ` Haitao Shan [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=BANLkTinab3aJwZHFu0qk8J6_faRuaM8UaA@mail.gmail.com \
--to=maillists.shan@gmail.com \
--cc=JBeulich@novell.com \
--cc=xen-devel@lists.xensource.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).