xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
	keir.xen@gmail.com, tim@xen.org
Subject: Re: [V1 PATCH 03/11] PVH dom0: iommu related changes
Date: Thu, 14 Nov 2013 17:43:00 -0800	[thread overview]
Message-ID: <20131114174300.56c070cf@mantra.us.oracle.com> (raw)
In-Reply-To: <528260A3020000780010288F@nat28.tlf.novell.com>

On Tue, 12 Nov 2013 16:08:51 +0000
"Jan Beulich" <JBeulich@suse.com> wrote:

> >>> On 09.11.13 at 02:23, Mukesh Rathor <mukesh.rathor@oracle.com>
> >>> wrote:
> > --- a/xen/drivers/passthrough/iommu.c
> > +++ b/xen/drivers/passthrough/iommu.c
> > @@ -125,15 +125,27 @@ int iommu_domain_init(struct domain *d)
> >      return hd->platform_ops->init(d);
> >  }
> >  
> > +static inline void check_dom0_pvh_reqs(struct domain *d)
> 
> No point for this to be an inline function. Even more, irrespective
> of whether it is, it should also be marked __init.

Ok, marked __init, removed inline. Or did you mean get
rid of the function and move checks to iommu_dom0_init()?

thanks,
m

  reply	other threads:[~2013-11-15  1:43 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-09  1:23 [V1 PATCH 0/11]: PVH dom0 Mukesh Rathor
2013-11-09  1:23 ` [V1 PATCH 01/11] PVH dom0: set eflags resvd bit #1 Mukesh Rathor
2013-11-12 16:19   ` Konrad Rzeszutek Wilk
2013-11-12 16:24     ` Jan Beulich
2013-11-12 16:31       ` Konrad Rzeszutek Wilk
2013-11-09  1:23 ` [V1 PATCH 02/11] PVH dom0: Allow physdevops for PVH dom0 Mukesh Rathor
2013-11-09  1:23 ` [V1 PATCH 03/11] PVH dom0: iommu related changes Mukesh Rathor
2013-11-12 16:08   ` Jan Beulich
2013-11-15  1:43     ` Mukesh Rathor [this message]
2013-11-15  7:36       ` Jan Beulich
2013-11-09  1:23 ` [V1 PATCH 04/11] PVH dom0: create update_memory_mapping() function Mukesh Rathor
2013-11-12 16:12   ` Jan Beulich
2013-11-15  1:59     ` Mukesh Rathor
2013-11-15  7:38       ` Jan Beulich
2013-11-09  1:23 ` [V1 PATCH 05/11] PVH dom0: move some pv specific code to static functions Mukesh Rathor
2013-11-09  1:23 ` [V1 PATCH 06/11] PVH dom0: construct_dom0 changes Mukesh Rathor
2013-11-12 16:13   ` Konrad Rzeszutek Wilk
2013-11-15  2:21     ` Mukesh Rathor
2013-11-15  7:59       ` Jan Beulich
2013-11-12 16:35   ` Jan Beulich
2013-11-15  2:34     ` Mukesh Rathor
2013-11-15  7:40       ` Jan Beulich
2013-11-09  1:23 ` [V1 PATCH 07/11] PVH dom0: implement XENMEM_add_to_physmap_range for x86 Mukesh Rathor
2013-11-12 16:46   ` Jan Beulich
2013-11-09  1:23 ` [V1 PATCH 08/11] PVH dom0: Introduce p2m_map_foreign Mukesh Rathor
2013-11-12 16:16   ` Konrad Rzeszutek Wilk
2013-11-09  1:23 ` [V1 PATCH 09/11] PVH dom0: Add and remove foreign pages Mukesh Rathor
2013-11-12 16:58   ` Jan Beulich
2013-11-09  1:23 ` [V1 PATCH 10/11] PVH dom0: add opt_dom0pvh to setup.c Mukesh Rathor
2013-11-12 16:18   ` Konrad Rzeszutek Wilk
2013-11-14 11:38 ` [V1 PATCH 0/11]: PVH dom0 Roger Pau Monné
2013-11-14 22:42   ` Mukesh Rathor
2013-11-15  7:55     ` Jan Beulich

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=20131114174300.56c070cf@mantra.us.oracle.com \
    --to=mukesh.rathor@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=keir.xen@gmail.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xenproject.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).