public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: akataria@vmware.com, "H. Peter Anvin" <hpa@zytor.com>,
	the arch/x86 maintainers <x86@kernel.org>,
	Zach Amsden <zach@vmware.com>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Rohit Jain <rjain@vmware.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PARAVIRT/x86] BUGFIX: Put a missing paravirt_release_pmd in pgd_dtor
Date: Fri, 6 Feb 2009 15:53:24 +0100	[thread overview]
Message-ID: <20090206145324.GF18368@elte.hu> (raw)
In-Reply-To: <498BDE1D.8030101@goop.org>


* Jeremy Fitzhardinge <jeremy@goop.org> wrote:

> Alok Kataria wrote:
>> As it affects only VMI, instead of adding another callback, i have
>> hooked on the paravirt_pgd_free call for vmi to release the pgd page.
>> Below is the patch. I will run some overnight tests with this patch and
>> get back if there are any errors.
>>   
>
> I'd forgotten that I'd already added pgd_alloc/pgd_free.  So, yes, just  
> use pgd_free.

Can i take that as an Acked-by?

	Ingo

  reply	other threads:[~2009-02-06 14:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-06  2:02 [PARAVIRT/x86] BUGFIX: Put a missing paravirt_release_pmd in pgd_dtor Alok Kataria
2009-02-06  2:30 ` Jeremy Fitzhardinge
2009-02-06  6:17   ` Alok Kataria
2009-02-06  6:52     ` Jeremy Fitzhardinge
2009-02-06 14:53       ` Ingo Molnar [this message]
2009-02-06 17:00         ` Jeremy Fitzhardinge
2009-02-06 18:29           ` Alok Kataria
2009-02-09 12:10             ` Ingo Molnar
2009-02-09 20:19               ` Alok Kataria
2009-02-11 12:48                 ` Ingo Molnar

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=20090206145324.GF18368@elte.hu \
    --to=mingo@elte.hu \
    --cc=akataria@vmware.com \
    --cc=hpa@zytor.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjain@vmware.com \
    --cc=rusty@rustcorp.com.au \
    --cc=x86@kernel.org \
    --cc=zach@vmware.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