From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rusty Russell Subject: Re: [RESENDx2] [PULL] virtio: fix barriers for virtio-mmio Date: Sat, 24 Dec 2011 13:31:14 +1030 Message-ID: <87pqfeisg5.fsf@rustcorp.com.au> References: <8739cbkgv2.fsf@rustcorp.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org To: Ohad Ben-Cohen , Linus Torvalds Cc: linux-kernel@vger.kernel.org, linux-arm , virtualization List-Id: virtualization@lists.linuxfoundation.org On Fri, 23 Dec 2011 13:35:26 +0200, Ohad Ben-Cohen wrote: > On Fri, Dec 23, 2011 at 11:35 AM, Linus Torvalds > wrote: > > On x86, there really is never any reason to use the heavy memory > > barriers unless you are talking to a real device. And last I saw, > > "virtio" was still about virtual IO. Not any more, as the commit message describes. But I missed that they're using rpmsg, which isn't merged yet. Sorry for the noise, Rusty. PS. Switching barriers by bus type is too crude anyway, let's come up with something better... From mboxrd@z Thu Jan 1 00:00:00 1970 From: rusty@rustcorp.com.au (Rusty Russell) Date: Sat, 24 Dec 2011 13:31:14 +1030 Subject: [RESENDx2] [PULL] virtio: fix barriers for virtio-mmio In-Reply-To: References: <8739cbkgv2.fsf@rustcorp.com.au> Message-ID: <87pqfeisg5.fsf@rustcorp.com.au> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Fri, 23 Dec 2011 13:35:26 +0200, Ohad Ben-Cohen wrote: > On Fri, Dec 23, 2011 at 11:35 AM, Linus Torvalds > wrote: > > On x86, there really is never any reason to use the heavy memory > > barriers unless you are talking to a real device. And last I saw, > > "virtio" was still about virtual IO. Not any more, as the commit message describes. But I missed that they're using rpmsg, which isn't merged yet. Sorry for the noise, Rusty. PS. Switching barriers by bus type is too crude anyway, let's come up with something better... From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755402Ab1LXDCe (ORCPT ); Fri, 23 Dec 2011 22:02:34 -0500 Received: from ozlabs.org ([203.10.76.45]:53210 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752015Ab1LXDCd (ORCPT ); Fri, 23 Dec 2011 22:02:33 -0500 From: Rusty Russell To: Ohad Ben-Cohen , Linus Torvalds Cc: linux-kernel@vger.kernel.org, virtualization , linux-arm Subject: Re: [RESENDx2] [PULL] virtio: fix barriers for virtio-mmio In-Reply-To: References: <8739cbkgv2.fsf@rustcorp.com.au> User-Agent: Notmuch/0.6.1-1 (http://notmuchmail.org) Emacs/23.3.1 (i686-pc-linux-gnu) Date: Sat, 24 Dec 2011 13:31:14 +1030 Message-ID: <87pqfeisg5.fsf@rustcorp.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 23 Dec 2011 13:35:26 +0200, Ohad Ben-Cohen wrote: > On Fri, Dec 23, 2011 at 11:35 AM, Linus Torvalds > wrote: > > On x86, there really is never any reason to use the heavy memory > > barriers unless you are talking to a real device. And last I saw, > > "virtio" was still about virtual IO. Not any more, as the commit message describes. But I missed that they're using rpmsg, which isn't merged yet. Sorry for the noise, Rusty. PS. Switching barriers by bus type is too crude anyway, let's come up with something better...