From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:45893) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZAH9w-0007ex-1w for qemu-devel@nongnu.org; Wed, 01 Jul 2015 08:30:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZAH9s-0006br-DW for qemu-devel@nongnu.org; Wed, 01 Jul 2015 08:30:35 -0400 Received: from mx1.redhat.com ([209.132.183.28]:42774) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZAH9s-0006bQ-84 for qemu-devel@nongnu.org; Wed, 01 Jul 2015 08:30:32 -0400 Message-ID: <1435753829.4160.41.camel@redhat.com> From: Gerd Hoffmann Date: Wed, 01 Jul 2015 14:30:29 +0200 In-Reply-To: <20150701100623-mutt-send-email-mst@redhat.com> References: <1435653553-7728-1-git-send-email-kraxel@redhat.com> <1435653553-7728-3-git-send-email-kraxel@redhat.com> <20150701100623-mutt-send-email-mst@redhat.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v2 02/22] virtio: run drivers in 32bit mode List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: seabios@seabios.org, qemu-devel@nongnu.org On Mi, 2015-07-01 at 10:08 +0200, Michael S. Tsirkin wrote: > On Tue, Jun 30, 2015 at 10:38:53AM +0200, Gerd Hoffmann wrote: > > virtio version 1.0 registers can (and actually do in the qemu > > implementation) live in mmio space. So we must run the blk and > > scsi virtio drivers in 32bit mode, otherwise we can't access them. > > > > This also allows to drop a bunch of GET_LOWFLAT calls from the virtio > > code in the following patches. > > > > Signed-off-by: Gerd Hoffmann > > Is there an advantage to running them in a 16 bit mode? Not really any more. Switching from 32bit mode back to whatever-was-active-before used to be problematic before we had smm mode support. In theory. Because you can't save/restore the complete x86 processor state. In practice we had surprisingly few problems, appearently linux boot loaders simply don't play dirty tricks. cheers, Gerd