From: Cornelia Huck <cohuck@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Jason J. Herne" <jjherne@linux.ibm.com>,
qemu-devel@nongnu.org, qemu-s390x@nongnu.org,
pasic@linux.ibm.com, alifm@linux.ibm.com, borntraeger@de.ibm.com
Subject: Re: [Qemu-devel] [qemu-s390x] [PATCH v5 01/15] s390 vfio-ccw: Add bootindex property and IPLB data
Date: Mon, 1 Apr 2019 10:51:53 +0200 [thread overview]
Message-ID: <20190401105153.0eef4fb9.cohuck@redhat.com> (raw)
In-Reply-To: <5961e42d-8574-48de-3057-6cd7680645cc@redhat.com>
On Tue, 26 Mar 2019 13:49:41 +0100
Thomas Huth <thuth@redhat.com> wrote:
> On 13/03/2019 17.31, Jason J. Herne wrote:
> > Add bootindex property and iplb data for vfio-ccw devices. This allows us to
> > forward boot information into the bios for vfio-ccw devices.
> >
> > Refactor s390_get_ccw_device() to return device type. This prevents us from
> > having to use messy casting logic in several places.
> >
> > Signed-off-by: Jason J. Herne <jjherne@linux.ibm.com>
> > Acked-by: Halil Pasic <pasic@linux.vnet.ibm.com>
> > Reviewed-by: Cornelia Huck <cohuck@redhat.com>
> > ---
> [...]
> > diff --git a/include/hw/s390x/vfio-ccw.h b/include/hw/s390x/vfio-ccw.h
> > new file mode 100644
> > index 0000000..2fceaa2
> > --- /dev/null
> > +++ b/include/hw/s390x/vfio-ccw.h
> > @@ -0,0 +1,28 @@
> > +/*
> > + * vfio based subchannel assignment support
> > + *
> > + * Copyright 2017 IBM Corp.
>
> Maybe bump the year to 2019 ?
Not sure, the code is simply extracted and not changed, isn't it?
(If bumped, it probably should be 2017,2019.)
>
> > + * Author(s): Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>
> > + * Xiao Feng Ren <renxiaof@linux.vnet.ibm.com>
> > + * Pierre Morel <pmorel@linux.vnet.ibm.com>
> > + *
> > + * This work is licensed under the terms of the GNU GPL, version 2 or (at
> > + * your option) any later version. See the COPYING file in the top-level
> > + * directory.
> > + */
> > +
> > +#ifndef HW_VFIO_CCW_H
> > +#define HW_VFIO_CCW_H
> > +
> > +#include "hw/vfio/vfio-common.h"
> > +#include "hw/s390x/s390-ccw.h"
> > +#include "hw/s390x/ccw-device.h"
> > +
> > +#define TYPE_VFIO_CCW "vfio-ccw"
> > +#define VFIO_CCW(obj) \
> > + OBJECT_CHECK(VFIOCCWDevice, (obj), TYPE_VFIO_CCW)
> > +
> > +#define TYPE_VFIO_CCW "vfio-ccw"
> > +typedef struct VFIOCCWDevice VFIOCCWDevice;
> > +
> > +#endif
>
> Reviewed-by: Thomas Huth <thuth@redhat.com>
next parent reply other threads:[~2019-04-01 8:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1552494682-16788-1-git-send-email-jjherne@linux.ibm.com>
[not found] ` <1552494682-16788-2-git-send-email-jjherne@linux.ibm.com>
[not found] ` <5961e42d-8574-48de-3057-6cd7680645cc@redhat.com>
2019-04-01 8:51 ` Cornelia Huck [this message]
[not found] ` <1552494682-16788-12-git-send-email-jjherne@linux.ibm.com>
[not found] ` <a52f522d-e161-f11f-a9b1-85f2ed2d0262@redhat.com>
2019-04-01 14:11 ` [Qemu-devel] [qemu-s390x] [PATCH v5 11/15] s390-bios: cio error handling Jason J. Herne
[not found] ` <1552494682-16788-16-git-send-email-jjherne@linux.ibm.com>
[not found] ` <fd2f7e0d-cfab-245e-8c06-9b9ed424b7e4@redhat.com>
2019-04-01 15:35 ` [Qemu-devel] [qemu-s390x] [PATCH v5 15/15] s390-bios: Support booting from real dasd device Jason J. Herne
2019-04-01 15:55 ` Thomas Huth
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=20190401105153.0eef4fb9.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=alifm@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=jjherne@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.com \
/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).