qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Thomas Huth <thuth@redhat.com>,
	QEMU Trivial <qemu-trivial@nongnu.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Greg Kurz <groug@kaod.org>
Subject: Re: [Qemu-devel] [PATCH] Separate function types from opaque types in include/qemu/typedefs.h
Date: Wed, 28 Jun 2017 11:32:20 +0200	[thread overview]
Message-ID: <8760fg790b.fsf@secure.mitica> (raw)
In-Reply-To: <87o9tf5gb8.fsf@dusky.pond.sub.org> (Markus Armbruster's message of "Fri, 23 Jun 2017 09:11:39 +0200")

Markus Armbruster <armbru@redhat.com> wrote:
> Peter Maydell <peter.maydell@linaro.org> writes:
>
>> On 22 June 2017 at 19:08, Thomas Huth <thuth@redhat.com> wrote:
>>> On 22.06.2017 19:50, Dr. David Alan Gilbert wrote:
>>>> Could do; I'm just not finding tiny header files with one or
>>>> two entries each that useful.
>>
>> Well, it means that the bulk of code that doesn't care about the
>> types doesn't get its compilation fractionally slowed by having
>> to parse the typedef anyway. In general I think we're drifting
>> towards "have each .c file get fewer things automatically" rather
>> than otherwise (eg more finely focused files rather than stuffing
>> everything into qemu-common.h).
>
> Yes.  See also "Our use of #include is undisciplined, and what to do
> about it"
> Message-ID: <87wpp4m6n1.fsf@blackfin.pond.sub.org>
> https://lists.nongnu.org/archive/html/qemu-devel/2016-03/msg03271.html
>
> I have some unfinished work towards emptying out qemu-common.h.  Need
> to find the time to finish it.
>
> [...]

YES!!!!!

Once there, we can also do other cleanups.

inclufde/sysemu/sysemu.h

have things not related at all.
I want to get rid of it on migration, because you know, we do zero
emulation there, but there are things like "runstate" that are defined
there.

I removed on that version lots of migration functionality that were
there, just from historical reasons, not because they belong there.

Later, Juan.

  reply	other threads:[~2017-06-28  9:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-22 16:06 [Qemu-devel] [PATCH] Separate function types from opaque types in include/qemu/typedefs.h Greg Kurz
2017-06-22 16:14 ` Peter Maydell
2017-06-22 16:42   ` Greg Kurz
2017-06-22 17:03     ` Juan Quintela
2017-06-22 17:22       ` Peter Maydell
2017-06-22 17:25         ` Dr. David Alan Gilbert
2017-06-22 17:46           ` Greg Kurz
2017-06-22 17:50             ` Dr. David Alan Gilbert
2017-06-22 18:08               ` Thomas Huth
2017-06-22 18:11                 ` Peter Maydell
2017-06-22 18:34                   ` Dr. David Alan Gilbert
2017-06-22 19:23                     ` Greg Kurz
2017-06-26  9:27                       ` Dr. David Alan Gilbert
2017-06-23  7:11                   ` Markus Armbruster
2017-06-28  9:32                     ` Juan Quintela [this message]
2017-06-23  7:04         ` Markus Armbruster

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=8760fg790b.fsf@secure.mitica \
    --to=quintela@redhat.com \
    --cc=armbru@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=groug@kaod.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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).