qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	qemu-s390x <qemu-s390x@nongnu.org>,
	Halil Pasic <pasic@linux.vnet.ibm.com>,
	Alexander Graf <agraf@suse.de>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] s390/kvm_virtio/linux-headers: remove traces of old virtio transport
Date: Thu, 16 Nov 2017 10:09:10 +0100	[thread overview]
Message-ID: <20171116100910.1a9e291a.cohuck@redhat.com> (raw)
In-Reply-To: <07ba2257-d6b4-2a57-1151-21f3a69b89d0@de.ibm.com>

On Thu, 16 Nov 2017 08:45:09 +0100
Christian Borntraeger <borntraeger@de.ibm.com> wrote:

> On 11/15/2017 06:10 PM, Cornelia Huck wrote:
> > On Wed, 15 Nov 2017 16:42:23 +0100
> > Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> >   
> >> We no longer support the old s390 transport, neither does the newest
> >> Linux kernel. Remove it from the linux header script as well as the
> >> s390x virtio code.  We still should handle the VIRTIO_NOTIFY hypercall,
> >> to tolerate early printk on older guest kernels without an sclp console.  
> > 
> > Are there any such guests still around? Wouldn't they be unable to run
> > because of the missing old transport anyway?  
> 
> As far as I can see even an 4.13 will do
> 
> static int __init s390_virtio_console_init(void)
> {
>         if (sclp.has_vt220 || sclp.has_linemode)
>                 return -ENODEV;
>         return virtio_cons_early_init(early_put_chars);
> }
> console_initcall(s390_virtio_console_init);
> 
> No matter if there is the old transport or not available.
> 
> So as soon as somebody chooses virtio-console you should see the diag500 from the early
> printk.

Grmpf, and the first condition does not trigger when you don't define
any sclp console.

Oh well, it seems we still have to drag this along :(
 
> >   
> >> We continue to ignore these events.
> >>
> >> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
> >> ---
> >>  hw/s390x/s390-virtio-hcall.h                   |  6 ++-
> >>  include/standard-headers/asm-s390/kvm_virtio.h | 64
> >> --------------------------
> >> scripts/update-linux-headers.sh                |  1 - 3 files
> >> changed, 4 insertions(+), 67 deletions(-) delete mode 100644
> >> include/standard-headers/asm-s390/kvm_virtio.h  
> >   

I think this becomes relevant only when someone does a headers update
against 4.15+, which is unlikely to happen in freeze. So I'll queue
this to s390-next only.

      reply	other threads:[~2017-11-16  9:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-15 15:42 [Qemu-devel] [PATCH] s390/kvm_virtio/linux-headers: remove traces of old virtio transport Christian Borntraeger
2017-11-15 17:10 ` Cornelia Huck
2017-11-16  7:45   ` Christian Borntraeger
2017-11-16  9:09     ` Cornelia Huck [this message]

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=20171116100910.1a9e291a.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=pasic@linux.vnet.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=rth@twiddle.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).