All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Egger <Christoph.Egger@amd.com>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] libxc: free thread specific hypercall buffer on xc_interface_close
Date: Thu, 19 Aug 2010 14:39:55 +0200	[thread overview]
Message-ID: <201008191439.56338.Christoph.Egger@amd.com> (raw)
In-Reply-To: <1282148788.3170.1221.camel@zakaz.uk.xensource.com>

On Wednesday 18 August 2010 18:26:28 Ian Campbell wrote:
> On Wed, 2010-08-18 at 17:04 +0100, Christoph Egger wrote:
> > This patch prevents me from starting a guest until
> > the outstanding issue - namely why is hcall_buf_prep() never called -
> > is solved.
>
> You wouldn't expect hcall_buf_prep to be called if you opened the xc
> interface and then closed it without doing a hypercall which required
> any locked down memory.
>
> This updated version of the patch was intended to handle exactly this
> case

Yes, it works. The issue was in the debug code itself. After
removing the trace code I am able to start guests again.

Thanks for your help.

> since it appears that under NetBSD it can cause issues. 

I am wondering why this issue didn't appear on Linux.
Does Linux have some kind of auto-initialization?

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

  reply	other threads:[~2010-08-19 12:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-18 15:01 [PATCH] libxc: free thread specific hypercall buffer on xc_interface_close Ian Campbell
2010-08-18 16:04 ` Christoph Egger
2010-08-18 16:26   ` Ian Campbell
2010-08-19 12:39     ` Christoph Egger [this message]
2010-08-19 12:48       ` Ian Campbell

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=201008191439.56338.Christoph.Egger@amd.com \
    --to=christoph.egger@amd.com \
    --cc=Ian.Campbell@eu.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.