From mboxrd@z Thu Jan 1 00:00:00 1970 From: mst@redhat.com (Michael S. Tsirkin) Date: Thu, 1 Dec 2011 11:09:21 +0200 Subject: [RFC] virtio: use mandatory barriers for remote processor vdevs In-Reply-To: References: <1322569886-13055-1-git-send-email-ohad@wizery.com> <20111129131110.GC19157@redhat.com> <20111129151958.GA31789@redhat.com> <20111130145004.GD21413@redhat.com> <20111130231306.GD30031@redhat.com> Message-ID: <20111201090920.GA8231@redhat.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Thu, Dec 01, 2011 at 08:14:26AM +0200, Ohad Ben-Cohen wrote: > On Thu, Dec 1, 2011 at 1:13 AM, Michael S. Tsirkin wrote: > > For x86, stores into memory are ordered. So I think that yes, smp_XXX > > can be selected at compile time. > > But then you can't use the same kernel image for both scenarios. I was talking about virtio-pci. That always allocates the ring in the normal memory. > It won't take long until people will use virtio on ARM for both > virtualization and for talking to devices, and having to rebuild the > kernel for different use cases is nasty. Yes, I understand that it's nasty. > _______________________________________________ > Virtualization mailing list > Virtualization at lists.linux-foundation.org > https://lists.linuxfoundation.org/mailman/listinfo/virtualization