All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Andre Przywara <andre.przywara@calxeda.com>,
	julien.grall@linaro.org, tim@xen.org, xen-devel@lists.xen.org,
	Anup Patel <apatel@apm.com>,
	Pranavkumar Sawargaonkar <psawargaonkar@apm.com>
Subject: Re: [PATCH v2] tools: libxc: flush data cache after loading images into guest memory
Date: Thu, 12 Dec 2013 14:37:36 +0000	[thread overview]
Message-ID: <1386859056.18946.15.camel@kazak.uk.xensource.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1312121430510.8667@kaball.uk.xensource.com>

On Thu, 2013-12-12 at 14:30 +0000, Stefano Stabellini wrote:
> On Thu, 12 Dec 2013, Ian Campbell wrote:
> > On ARM guest OSes are started with MMU and Caches disables (as they are on
> > native) however caching is enabled in the domain running the builder and
> > therefore we must flush the cache as we load the blobs, otherwise when the
> > guest starts running it may not see them. The dom0 build in the hypervisor has
> > the same requirements and already does the right thing.
> > 
> > The mechanism for performing a cache flush from userspace is OS specific, so
> > implement this as a new osdep hook:
> > 
> >  - On 32-bit ARM Linux provides a system call to flush the cache.
> >  - On 64-bit ARM Linux the processor is configured to allow cache flushes
> >    directly from userspace.
> >  - Non-Linux platforms will need to provide their own implementation. If
> >    similar mechanisms are not available then a new privcmd ioctl should be a
> >    suitable alternative.
> > 
> > No cache maintenance is required on x86, so provide a stub for all non-Linux
> > platforms which returns success on x86 only and log an error otherwise.
> > 
> > This fixes guest building on Xgene which has a very large L3 cache and so is
> > particularly susceptible to this problem. It has also been observed
> > sporadically on midway.
> > 
> > Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> > Cc: Andre Przywara <andre.przywara@calxeda.com>
> > Cc: Pranavkumar Sawargaonkar <psawargaonkar@apm.com>
> > Cc: Anup Patel <apatel@apm.com>
> 
> Looks good to me

Is that an Ack?

  reply	other threads:[~2013-12-12 14:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-12 12:21 [PATCH] tools: libxc: flush data cache after loading images into guest memory Ian Campbell
2013-12-12 14:11 ` Julien Grall
2013-12-12 14:23 ` [PATCH v2] " Ian Campbell
2013-12-12 14:30   ` Stefano Stabellini
2013-12-12 14:37     ` Ian Campbell [this message]
2013-12-12 14:45       ` Stefano Stabellini
2013-12-12 14:49         ` Ian Campbell
2013-12-12 17:31   ` Ian Campbell
2013-12-12 17:52     ` Ian Jackson
2013-12-12 19:32       ` Ian Campbell
2013-12-12 19:43         ` Ian Jackson
2013-12-12 17:33   ` Ian Campbell
2013-12-13  0:49   ` Julien Grall
2013-12-13  8:26     ` Ian Campbell
2013-12-13 12:01       ` Stefano Stabellini
2013-12-13 12:53         ` Ian Campbell
2013-12-16  0:49           ` Julien Grall
2013-12-16 11:05             ` 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=1386859056.18946.15.camel@kazak.uk.xensource.com \
    --to=ian.campbell@citrix.com \
    --cc=andre.przywara@calxeda.com \
    --cc=apatel@apm.com \
    --cc=julien.grall@linaro.org \
    --cc=psawargaonkar@apm.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xen.org \
    /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.