From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Konrad Rzeszutek Wilk <konrad@kernel.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH 6/8] docs: Document the dom0_vga_console_info structure.
Date: Wed, 30 Jan 2013 12:10:36 -0500 [thread overview]
Message-ID: <20130130171036.GA2217@konrad-lan.dumpdata.com> (raw)
In-Reply-To: <1359451898.12252.44.camel@zakaz.uk.xensource.com>
On Tue, Jan 29, 2013 at 09:31:38AM +0000, Ian Campbell wrote:
> On Mon, 2013-01-28 at 18:32 +0000, Konrad Rzeszutek Wilk wrote:
> > Mark-up for inclusion of generated docs.
> >
> > Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> > ---
> > xen/include/public/xen.h | 10 +++++++++-
> > 1 file changed, 9 insertions(+), 1 deletion(-)
> >
> > diff --git a/xen/include/public/xen.h b/xen/include/public/xen.h
> > index e1748d1..c50bbfc 100644
> > --- a/xen/include/public/xen.h
> > +++ b/xen/include/public/xen.h
> > @@ -779,7 +779,15 @@ struct xen_multiboot_mod_list
> > /* Unused, must be zero */
> > uint32_t pad;
> > };
> > -
> > +/*
> > + * `incontents 200 startofday_dom0_console Dom9_console
> > + *
> > + * The console structure in start_info.console.dom0
> > + *
> > + * The contents off this structure follows mostly the Linux kernel
> > + * bootparam structure and includes a variety of information required
> > + * to have a working VGA/VESA console.
>
> Would it be useful to either link to the bootparam structure information
> or to explain from first principals? I suppose the existing fields are
> actually reasonably well commented.
>
> NB, ./arch/x86/include/uapi/asm/bootparam.h doesn't seem to have a
> literal struct bootparam so I guess you are referring to something else?
> There is a struct boot_params but it doesn't really match what is here.
> There is a struct screen_info in Linux but it isn't a good match for
> this Xen structure either.
>
> Are you sure it mostly follows a Linux bootparam structure? Maybe it
No. I confused it with another structure that is retrievied via the
XENPF_firmware_info hypercall.
> would be easiest to just say:
>
> This structure includes a variety of information required to
> have a working VGA/VESA console.
>
Perect.
> ?
>
>
next prev parent reply other threads:[~2013-01-30 17:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-28 18:32 [DOCS/PATCH] http://wiki.xen.org/wiki/X86_Paravirtualised_Memory_Management changes Konrad Rzeszutek Wilk
2013-01-28 18:32 ` [PATCH 1/8] docs: Document the ELF notes Konrad Rzeszutek Wilk
2013-01-29 9:16 ` Ian Campbell
2013-01-28 18:32 ` [PATCH 2/8] docs: Provide some examples of the various ELF values Konrad Rzeszutek Wilk
2013-01-29 9:23 ` Ian Campbell
2013-01-28 18:32 ` [PATCH 3/8] docs: Document the ELF_FEATURES entry Konrad Rzeszutek Wilk
2013-01-29 9:23 ` Ian Campbell
2013-01-28 18:32 ` [PATCH 4/8] docs: Add some extra details to the ELF note Konrad Rzeszutek Wilk
2013-01-29 9:26 ` Ian Campbell
2013-01-28 18:32 ` [PATCH 5/8] docs: Document the shared structure Konrad Rzeszutek Wilk
2013-01-29 9:26 ` Ian Campbell
2013-01-28 18:32 ` [PATCH 6/8] docs: Document the dom0_vga_console_info structure Konrad Rzeszutek Wilk
2013-01-29 9:31 ` Ian Campbell
2013-01-30 17:10 ` Konrad Rzeszutek Wilk [this message]
2013-01-28 18:32 ` [PATCH 7/8] docs: Document start_info changes in Xen 4.2 Konrad Rzeszutek Wilk
2013-01-29 9:37 ` Ian Campbell
2013-01-30 17:23 ` Konrad Rzeszutek Wilk
2013-01-31 9:58 ` Ian Campbell
2013-01-28 18:32 ` [PATCH 8/8] docs: Document the XenBus structure Konrad Rzeszutek Wilk
2013-01-29 9:38 ` Ian Campbell
2013-01-29 10:05 ` [DOCS/PATCH] http://wiki.xen.org/wiki/X86_Paravirtualised_Memory_Management changes Ian Campbell
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=20130130171036.GA2217@konrad-lan.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=konrad@kernel.org \
--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 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.