public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@sgi.com>
To: "Zhang, Xiantao" <xiantao.zhang@intel.com>
Cc: Avi Kivity <avi@qumranet.com>, "Luck, Tony" <tony.luck@intel.com>,
	"Xu, Anthony" <anthony.xu@intel.com>,
	Akio Takebe <takebe_akio@jp.fujitsu.com>,
	kvm-devel@lists.sourceforge.net,
	kvm-ia64-devel@lists.sourceforge.net, linux-ia64@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	Carsten Otte <cotte@de.ibm.com>
Subject: Re: [03/15][PATCH] kvm/ia64: Add header files for kvm/ia64. V8
Date: Mon, 31 Mar 2008 13:41:45 +0200	[thread overview]
Message-ID: <47F0CDF9.3040202@sgi.com> (raw)
In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDC01048243@pdsmsx415.ccr.corp.intel.com>

Hi Xiantao,

Some more nit-picking, though some of this is a bit more important
to fixup.

Cheers,
Jes


> +typedef struct thash_data {

Urgh! argh! Please avoid typedefs unless you really need them, see
Chapter 5 of Documentation/CodingStyle for details.

> diff --git a/include/asm-ia64/kvm_host.h b/include/asm-ia64/kvm_host.h
> new file mode 100644
> index 0000000..522bde0
> --- /dev/null
> +++ b/include/asm-ia64/kvm_host.h
> @@ -0,0 +1,530 @@
> +/* -*-  Mode:C; c-basic-offset:4; tab-width:4; indent-tabs-mode:nil -*-
> */

The standard indentation for Linux is 8 characters using tabs. If
possible it's preferred to comply with that to make the entire kernel
tree easier for everybody to deal with. See CodingStyle for details.

> +struct kvm_mmio_req {
> +	uint64_t addr;          /*  physical address		*/
> +	uint64_t size;          /*  size in bytes		*/
> +	uint64_t data;          /*  data (or paddr of data)     */
> +	uint8_t state:4;
> +	uint8_t dir:1;          /*  1=read, 0=write             */
> +};
> +typedef struct kvm_mmio_req mmio_req_t;

More typedefs

> +/*Pal data struct */
> +typedef struct pal_call{

and again.

> +	/*In area*/
> +	uint64_t gr28;
> +	uint64_t gr29;
> +	uint64_t gr30;
> +	uint64_t gr31;
> +	/*Out area*/
> +	struct ia64_pal_retval ret;
> +} pal_call_t;
> +
> +/* Sal data structure */
> +typedef struct sal_call{
and again...

> +	/*In area*/
> +	uint64_t in0;
> +	uint64_t in1;
> +	uint64_t in2;
> +	uint64_t in3;
> +	uint64_t in4;
> +	uint64_t in5;
> +	uint64_t in6;
> +	uint64_t in7;
> +	/*Our area*/
> +	struct sal_ret_values ret;
> +} sal_call_t;

       reply	other threads:[~2008-03-31 11:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <42DFA526FC41B1429CE7279EF83C6BDC01048243@pdsmsx415.ccr.corp.intel.com>
2008-03-31 11:41 ` Jes Sorensen [this message]
2008-03-31 13:46 ` [03/15][PATCH] kvm/ia64: Add header files for kvm/ia64. V8 Carsten Otte
2008-04-01  1:37   ` [kvm-ia64-devel] [03/15][PATCH] kvm/ia64: Add header files forkvm/ia64. V8 Zhang, Xiantao
2008-03-31  8:25 [03/15][PATCH] kvm/ia64: Add header files for kvm/ia64. V8 Zhang, Xiantao

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=47F0CDF9.3040202@sgi.com \
    --to=jes@sgi.com \
    --cc=anthony.xu@intel.com \
    --cc=avi@qumranet.com \
    --cc=cotte@de.ibm.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=kvm-ia64-devel@lists.sourceforge.net \
    --cc=linux-ia64@vger.kernel.org \
    --cc=takebe_akio@jp.fujitsu.com \
    --cc=tony.luck@intel.com \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=xiantao.zhang@intel.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