qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: qemu-s390x@nongnu.org, qemu-devel@nongnu.org,
	Richard Henderson <rth@twiddle.net>,
	Alexander Graf <agraf@suse.de>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Thomas Huth <thuth@redhat.com>,
	"Jason J . Herne" <jjherne@linux.ibm.com>,
	"Collin L . Walling" <walling@linux.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v1 1/7] s390x/tod: factor out TOD into separate device
Date: Mon, 4 Jun 2018 14:14:34 +0200	[thread overview]
Message-ID: <20180604141434.508e2f55.cohuck@redhat.com> (raw)
In-Reply-To: <a26f4c5e-59b2-078d-19a3-e73dbece67c1@redhat.com>

On Mon, 4 Jun 2018 14:00:43 +0200
David Hildenbrand <david@redhat.com> wrote:

> On 04.06.2018 13:38, Cornelia Huck wrote:
> > On Fri, 25 May 2018 13:37:02 +0200
> > David Hildenbrand <david@redhat.com> wrote:
> >   
> >> Let's treat this like a separate device. TCG will have to store the
> >> actual state/time later on.
> >>
> >> Include cpu-qom.h in kvm_s390x.h (due to S390CPU) to compile tod-kvm.c.  
> > 
> > Can't you include it in tod-kvm.c instead? Why was it not needed before?  
> 
> Guess I can, kvm_s390x.h looks to me like the right place, as S390CPU is
> used in there.
> 
> All other users include "cpu.h" already, so it isn't needed.

Hm, and for kvm_s390_irq, this file is using a forward declaration,
which would likely be more awkward for this structure.

Header dependencies are always fun :)

  reply	other threads:[~2018-06-04 12:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-25 11:37 [Qemu-devel] [PATCH v1 0/7] s390x: TOD refactoring + TCG CPU hotplug support David Hildenbrand
2018-05-25 11:37 ` [Qemu-devel] [PATCH v1 1/7] s390x/tod: factor out TOD into separate device David Hildenbrand
2018-06-04 11:38   ` Cornelia Huck
2018-06-04 12:00     ` David Hildenbrand
2018-06-04 12:14       ` Cornelia Huck [this message]
2018-06-07 10:49         ` [Qemu-devel] [qemu-s390x] " David Hildenbrand
2018-06-07 11:10           ` Cornelia Huck
2018-05-25 11:37 ` [Qemu-devel] [PATCH v1 2/7] s390x/tcg: drop tod_basetime David Hildenbrand
2018-05-25 11:37 ` [Qemu-devel] [PATCH v1 3/7] s390x/tcg: properly implement the TOD David Hildenbrand
2018-06-04 11:57   ` Cornelia Huck
2018-06-04 11:59     ` David Hildenbrand
2018-05-25 11:37 ` [Qemu-devel] [PATCH v1 4/7] s390x/tcg: SET CLOCK COMPARATOR can clear CKC interrupts David Hildenbrand
2018-05-25 11:37 ` [Qemu-devel] [PATCH v1 5/7] s390x/tcg: implement SET CLOCK David Hildenbrand
2018-06-04 12:05   ` Cornelia Huck
2018-06-07 10:48     ` [Qemu-devel] [qemu-s390x] " David Hildenbrand
2018-06-07 11:15       ` Cornelia Huck
2018-05-25 11:37 ` [Qemu-devel] [PATCH v1 6/7] s390x/tcg: rearm the CKC timer during migration David Hildenbrand
2018-06-04 12:09   ` Cornelia Huck
2018-06-07 10:47     ` [Qemu-devel] [qemu-s390x] " David Hildenbrand
2018-05-25 11:37 ` [Qemu-devel] [PATCH v1 7/7] s390x/tcg: fix CPU hotplug with single-threaded TCG David Hildenbrand

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=20180604141434.508e2f55.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=agraf@suse.de \
    --cc=borntraeger@de.ibm.com \
    --cc=david@redhat.com \
    --cc=jjherne@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=thuth@redhat.com \
    --cc=walling@linux.ibm.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).