From: Olaf Hering <olaf@aepfle.de>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH] xen pv-on-hvm: add pfn_is_ram helper for kdump
Date: Thu, 12 Jul 2012 19:44:11 +0200 [thread overview]
Message-ID: <20120712174411.GA24313@aepfle.de> (raw)
In-Reply-To: <20120712172424.GA5895@phenom.dumpdata.com>
On Thu, Jul 12, Konrad Rzeszutek Wilk wrote:
> > +++ b/include/xen/interface/hvm/hvm_op.h
> > @@ -43,4 +43,24 @@ struct xen_hvm_pagetable_dying {
> > typedef struct xen_hvm_pagetable_dying xen_hvm_pagetable_dying_t;
> > DEFINE_GUEST_HANDLE_STRUCT(xen_hvm_pagetable_dying_t);
> >
> > +typedef enum {
> > + HVMMEM_ram_rw, /* Normal read/write guest RAM */
> > + HVMMEM_ram_ro, /* Read-only; writes are discarded */
> > + HVMMEM_mmio_dm, /* Reads and write go to the device model */
> > +} hvmmem_type_t;
>
> Does this have to be a typdef?
>
> > +
> > +#define HVMOP_get_mem_type 15
> > +/* Return hvmmem_type_t for the specified pfn. */
> > +struct xen_hvm_get_mem_type {
> > + /* Domain to be queried. */
> > + domid_t domid;
> > + /* OUT variable. */
> > + uint16_t mem_type;
> > + uint16_t pad[2]; /* align next field on 8-byte boundary */
> > + /* IN variable. */
> > + uint64_t pfn;
> > +};
> > +typedef struct xen_hvm_get_mem_type xen_hvm_get_mem_type_t;
>
> Please no typdefs. I can fix this up, but in the future pls don't add
> more of them.
Its just a forward port from what went into linux-2.6.18.
Olaf
next prev parent reply other threads:[~2012-07-12 17:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 17:20 [PATCH] xen pv-on-hvm: add pfn_is_ram helper for kdump Olaf Hering
2012-07-12 17:24 ` [Xen-devel] " Konrad Rzeszutek Wilk
2012-07-12 17:44 ` Olaf Hering [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-12 9:00 Olaf Hering
2012-07-12 13:47 ` [Xen-devel] " Konrad Rzeszutek Wilk
2012-07-12 14:22 ` Olaf Hering
2012-07-12 14:21 ` Konrad Rzeszutek Wilk
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=20120712174411.GA24313@aepfle.de \
--to=olaf@aepfle.de \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.