All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@sgi.com>
To: "Zhang, Xiantao" <xiantao.zhang@intel.com>
Cc: Carsten Otte <cotte@de.ibm.com>,
	"Luck, Tony" <tony.luck@intel.com>,
	linux-ia64@vger.kernel.org, kvm-ia64-devel@lists.sourceforge.net,
	kvm-devel@lists.sourceforge.net, Avi Kivity <avi@qumranet.com>,
	virtualization@lists.linux-foundation.org
Subject: Re: [16/18]KVM:IA64 : Add kvm sal/pal virtulization support.V9
Date: Tue, 01 Apr 2008 15:26:18 +0000	[thread overview]
Message-ID: <47F2541A.50007@sgi.com> (raw)
In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDC0104872F@pdsmsx415.ccr.corp.intel.com>

Zhang, Xiantao wrote:
>>From 5c70c038c57190144390ae9d30c3d06afba103d4 Mon Sep 17 00:00:00 2001
> From: Xiantao Zhang <xiantao.zhang@intel.com>
> Date: Tue, 1 Apr 2008 14:59:30 +0800
> Subject: [PATCH] KVM:IA64 : Add kvm sal/pal virtulization support.
> 
> Some sal/pal calls would be traped to kvm for virtulization
> from guest firmware.
> Signed-off-by: Xiantao Zhang <xiantao.zhang@intel.com>
> ---
>  arch/ia64/kvm/kvm_fw.c |  500

Hi Xiantao,

A few more comments:


> --- /dev/null
> +++ b/arch/ia64/kvm/kvm_fw.c

> +static void kvm_get_pal_call_data(struct kvm_vcpu *vcpu,
> +		u64 *gr28, u64 *gr29, u64 *gr30, u64 *gr31) {
> +	struct exit_ctl_data *p;
> +
> +	if (vcpu) {
> +		p = &vcpu->arch.exit_data;
> +		if (p->exit_reason = EXIT_REASON_PAL_CALL) {
> +			*gr28 = p->u.pal_data.gr28;
> +			*gr29 = p->u.pal_data.gr29;
> +			*gr30 = p->u.pal_data.gr30;
> +			*gr31 = p->u.pal_data.gr31;
> +			return ;
> +		}
> +	}
> +	printk(KERN_DEBUG"Error occurs in kvm_get_pal_call_data!!\n");

Maybe make this error message a bit more elaborate with information
about what the error is?

> +static void set_sal_result(struct kvm_vcpu *vcpu,
> +		struct sal_ret_values result) {
> +	struct exit_ctl_data *p;
> +
> +	p = kvm_get_exit_data(vcpu);
> +	if (p && p->exit_reason = EXIT_REASON_SAL_CALL) {
> +		p->u.sal_data.ret = result;
> +		return ;
> +	}
> +	printk(KERN_WARNING"Error occurs!!!\n");

I love this error message :-) Seriously though, please make it say
where it is and what has been detected.

Cheers,
Jes

WARNING: multiple messages have this Message-ID (diff)
From: Jes Sorensen <jes@sgi.com>
To: "Zhang, Xiantao" <xiantao.zhang@intel.com>
Cc: Carsten Otte <cotte@de.ibm.com>,
	"Luck, Tony" <tony.luck@intel.com>,
	linux-ia64@vger.kernel.org, kvm-ia64-devel@lists.sourceforge.net,
	kvm-devel@lists.sourceforge.net, Avi Kivity <avi@qumranet.com>,
	virtualization@lists.linux-foundation.org
Subject: Re: [16/18]KVM:IA64 : Add kvm sal/pal virtulization support.V9
Date: Tue, 01 Apr 2008 17:26:18 +0200	[thread overview]
Message-ID: <47F2541A.50007@sgi.com> (raw)
In-Reply-To: <42DFA526FC41B1429CE7279EF83C6BDC0104872F@pdsmsx415.ccr.corp.intel.com>

Zhang, Xiantao wrote:
>>From 5c70c038c57190144390ae9d30c3d06afba103d4 Mon Sep 17 00:00:00 2001
> From: Xiantao Zhang <xiantao.zhang@intel.com>
> Date: Tue, 1 Apr 2008 14:59:30 +0800
> Subject: [PATCH] KVM:IA64 : Add kvm sal/pal virtulization support.
> 
> Some sal/pal calls would be traped to kvm for virtulization
> from guest firmware.
> Signed-off-by: Xiantao Zhang <xiantao.zhang@intel.com>
> ---
>  arch/ia64/kvm/kvm_fw.c |  500

Hi Xiantao,

A few more comments:


> --- /dev/null
> +++ b/arch/ia64/kvm/kvm_fw.c

> +static void kvm_get_pal_call_data(struct kvm_vcpu *vcpu,
> +		u64 *gr28, u64 *gr29, u64 *gr30, u64 *gr31) {
> +	struct exit_ctl_data *p;
> +
> +	if (vcpu) {
> +		p = &vcpu->arch.exit_data;
> +		if (p->exit_reason == EXIT_REASON_PAL_CALL) {
> +			*gr28 = p->u.pal_data.gr28;
> +			*gr29 = p->u.pal_data.gr29;
> +			*gr30 = p->u.pal_data.gr30;
> +			*gr31 = p->u.pal_data.gr31;
> +			return ;
> +		}
> +	}
> +	printk(KERN_DEBUG"Error occurs in kvm_get_pal_call_data!!\n");

Maybe make this error message a bit more elaborate with information
about what the error is?

> +static void set_sal_result(struct kvm_vcpu *vcpu,
> +		struct sal_ret_values result) {
> +	struct exit_ctl_data *p;
> +
> +	p = kvm_get_exit_data(vcpu);
> +	if (p && p->exit_reason == EXIT_REASON_SAL_CALL) {
> +		p->u.sal_data.ret = result;
> +		return ;
> +	}
> +	printk(KERN_WARNING"Error occurs!!!\n");

I love this error message :-) Seriously though, please make it say
where it is and what has been detected.

Cheers,
Jes

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace

  reply	other threads:[~2008-04-01 15:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01 10:52 [16/18]KVM:IA64 : Add kvm sal/pal virtulization support.V9 Zhang, Xiantao
2008-04-01 15:26 ` Jes Sorensen [this message]
2008-04-01 15:26   ` Jes Sorensen
2008-04-02  3:13   ` [kvm-ia64-devel] [16/18]KVM:IA64 : Add kvm sal/palvirtulization support.V9 Zhang, Xiantao
2008-04-02  3:13     ` Zhang, Xiantao
2008-04-01 15:26 ` [16/18]KVM:IA64 : Add kvm sal/pal virtulization support.V9 Jes Sorensen
  -- strict thread matches above, loose matches on Subject: below --
2008-04-01 10:52 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=47F2541A.50007@sgi.com \
    --to=jes@sgi.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=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 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.