All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arun Sharma <arun.sharma@intel.com>
To: Michael A Fetterman <Michael.Fetterman@cl.cam.ac.uk>
Cc: "Ling, Xiaofeng" <xiaofeng.ling@intel.com>,
	xen-devel@lists.xensource.com
Subject: Re: Re: Should shadow_lock be spin_lock_recursive?
Date: Fri, 13 May 2005 15:40:30 -0700	[thread overview]
Message-ID: <42852CDE.7000204@intel.com> (raw)
In-Reply-To: <E1DWDHb-0005Pi-00@mta1.cl.cam.ac.uk>

Michael A Fetterman wrote:
> 
> However, those calls to put_page(X) should never result in calls
> to free_domheap_pages(), as X's refcount should always be >= 1
> because of the get_page performed in free_dom_mem().
> 
> So that tells me the refcount on X was already broken before we got
> here...
> 

Thanks for the explanation. It was a patched xen that we were testing 
and the problem may have been caused by our patch. We'll try to look 
closely at the patch to figure out why the refrence counts were wrong.

	-Arun

      reply	other threads:[~2005-05-13 22:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-11 17:42 Should shadow_lock be spin_lock_recursive? Arun Sharma
2005-05-12  1:57 ` Xiaofeng Ling
2005-05-12  7:57   ` Keir Fraser
2005-05-12 12:59   ` Michael A Fetterman
2005-05-13 22:40     ` Arun Sharma [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=42852CDE.7000204@intel.com \
    --to=arun.sharma@intel.com \
    --cc=Michael.Fetterman@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.com \
    --cc=xiaofeng.ling@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.