Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753636Ab3EMC53 (ORCPT ); Sun, 12 May 2013 22:57:29 -0400 Received: from ozlabs.org ([203.10.76.45]:50686 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752782Ab3EMC50 (ORCPT ); Sun, 12 May 2013 22:57:26 -0400 From: Rusty Russell To: Pranavkumar Sawargaonkar , linux-arm-kernel@lists.infradead.org Cc: kvmarm@lists.cs.columbia.edu, linux-kernel@vger.kernel.org, linaro-kernel@lists.linaro.org, patches@linaro.org, anup.patel@linaro.org, amit.shah@redhat.com, Pranavkumar Sawargaonkar Subject: Re: [PATCH V2 2/3] Documentation: virtio: Add emergency write (emerg_wr) config register in virtio console. In-Reply-To: <1367842791-30285-3-git-send-email-pranavkumar@linaro.org> References: <1367842791-30285-1-git-send-email-pranavkumar@linaro.org> <1367842791-30285-3-git-send-email-pranavkumar@linaro.org> User-Agent: Notmuch/0.15.2+81~gd2c8818 (http://notmuchmail.org) Emacs/23.4.1 (i686-pc-linux-gnu) Date: Mon, 13 May 2013 12:22:07 +0930 Message-ID: <8761yn382w.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 Content-Length: 2327 Lines: 58 Pranavkumar Sawargaonkar writes: > Signed-off-by: Pranavkumar Sawargaonkar > Signed-off-by: Anup Patel > --- > Documentation/virtual/virtio-spec.txt | 8 +++++++- > 1 file changed, 7 insertions(+), 1 deletion(-) OK, I applied this to the lyx master, with three changes: 1) Changed "filed" to "field". 2) Added ", or even acknowledging the feature" after "without initializing virtio queues". 3) Added an initial point to the Device Initialization section: 1. If the VIRTIO_CONSOLE_F_EMERG_WRITE feature is offered, the emerg_wr field of the configuration can be written at any time. Thus it should work for very early boot debugging output as well as catastophic OS failures (eg. virtio ring corruption). Thanks, Rusty. > diff --git a/Documentation/virtual/virtio-spec.txt b/Documentation/virtual/virtio-spec.txt > index 0d6ec85..3ca38f8 100644 > --- a/Documentation/virtual/virtio-spec.txt > +++ b/Documentation/virtual/virtio-spec.txt > @@ -1927,11 +1927,16 @@ Ports 2 onwards only if VIRTIO_CONSOLE_F_MULTIPORT is set > ports; configuration fields nr_ports and max_nr_ports are > valid and control virtqueues will be used. > > + VIRTIO_CONSOLE_F_EMERG_WRITE(2) Device has support for emergency > + write. Configuration filed emerg_wr is valid. > + > Device configuration layout The size of the console is supplied > in the configuration space if the VIRTIO_CONSOLE_F_SIZE feature > is set. Furthermore, if the VIRTIO_CONSOLE_F_MULTIPORT feature > is set, the maximum number of ports supported by the device can > - be fetched.struct virtio_console_config { > + be fetched. If VIRTIO_CONSOLE_F_EMERG_WRITE is set then one can > + use emergency write to output single character without initializing > + virtio queues. struct virtio_console_config { > > u16 cols; > > @@ -1941,6 +1946,7 @@ Ports 2 onwards only if VIRTIO_CONSOLE_F_MULTIPORT is set > > u32 max_nr_ports; > > + u32 emerg_wr; > }; > > Device Initialization > -- > 1.7.9.5 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/