From: Christoph Egger <Christoph.Egger@amd.com>
To: Tim Deegan <Tim.Deegan@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 05/14] Nested Virtualization: core
Date: Tue, 10 Aug 2010 10:36:59 +0200 [thread overview]
Message-ID: <201008101037.00389.Christoph.Egger@amd.com> (raw)
In-Reply-To: <20100809123848.GY13291@whitby.uk.xensource.com>
Hi Tim,
It looks like I have missed this from your first review. Thanks for bringing
this up again.
On Monday 09 August 2010 14:38:48 Tim Deegan wrote:
> Hi,
>
> > +int
> > +nestedhvm_vcpu_destroy(struct vcpu *v)
> > +{
> > + int ret = 0;
> > +
> > + if (!nestedhvm_enabled(v->domain))
> > + return 0;
> > +
> > + if (nestedhvm_vcpu_in_guestmode(v)) {
> > + nestedhvm_vcpu_exit_guestmode(v);
> > + ret = -EBUSY;
> > + }
>
> This still bothers me, since we go on to complete the teardown anyway,
> and this function's only caller does nothing interesting with the
> result.
I removed "vcpu in guestmode" check completely.
> > + /* Enable interrupts or the guest won't see any interrupts
> > + * after nested guest exited.
> > + */
> > + nestedsvm_vcpu_stgi(v);
This stgi call is gone.
> > +
> > + hvm_nestedhvm_vcpu_destroy(v);
>
> While I'm complaining about unchecked return values, I should point out
> that your implementation of this returns an integer (which in turn is
> always 0).
I changed this to 'return hvm_nestedhvm_vcpu_destroy(v);'
> > + return ret;
This return is gone.
> > +}
Christoph
--
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
prev parent reply other threads:[~2010-08-10 8:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 15:01 [PATCH 05/14] Nested Virtualization: core Christoph Egger
2010-08-09 12:38 ` Tim Deegan
2010-08-10 8:36 ` Christoph Egger [this message]
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=201008101037.00389.Christoph.Egger@amd.com \
--to=christoph.egger@amd.com \
--cc=Tim.Deegan@citrix.com \
--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.