qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Rename qemu -> qemu-system-i386
Date: Fri, 02 Sep 2011 10:39:55 -0500	[thread overview]
Message-ID: <4E60F8CB.9080707@us.ibm.com> (raw)
In-Reply-To: <CAAu8pHs+esNEpu_1cr0BL2pA4_trP7GcSTBD8qeoB9CTkhmAgw@mail.gmail.com>

On 08/30/2011 02:24 PM, Blue Swirl wrote:
> On Mon, Aug 29, 2011 at 2:55 PM, Anthony Liguori<aliguori@us.ibm.com>  wrote:
>> This has been discussed before in the past.  The special casing really makes no
>> sense anymore.  This seems like a good change to make for 1.0.
>>
>> Signed-off-by: Anthony Liguori<aliguori@us.ibm.com>
>> ---
>>   Makefile        |    5 ++---
>>   Makefile.target |    4 ----
>>   2 files changed, 2 insertions(+), 7 deletions(-)
>>
>> diff --git a/Makefile b/Makefile
>> index 8606849..51ecdb5 100644
>> --- a/Makefile
>> +++ b/Makefile
>> @@ -365,9 +365,8 @@ tar:
>>         rm -rf /tmp/$(FILE)
>>
>>   SYSTEM_TARGETS=$(filter %-softmmu,$(TARGET_DIRS))
>> -SYSTEM_PROGS=$(patsubst qemu-system-i386,qemu, \
>> -             $(patsubst %-softmmu,qemu-system-%, \
>> -             $(SYSTEM_TARGETS)))
>> +SYSTEM_PROGS=$(patsubst %-softmmu,qemu-system-%, \
>> +             $(SYSTEM_TARGETS))
>
> Maybe the patsubst could be avoided, just rename the build directory
> from *-softmmu to qemu-system-* while at it?
>
>>
>>   USER_TARGETS=$(filter %-user,$(TARGET_DIRS))
>>   USER_PROGS=$(patsubst %-bsd-user,qemu-%, \
>
> Also here the directory and executable names could be made to match.

I thought that historically the phrase softmmu was for the variant of 
libcpu that had an emulated TLB.

I know Peter's been talking about a linux-user mode that uses softmmu 
since certain combinations of architectures today are impossible with 
linux-user (ia64 on x86_64 for instance).

So I think the current naming conventions probably are reasonable 
although I'm not opposed to changing them.  I think that should be a 
separate patch though.

Regards,

Anthony Liguori

>
>> diff --git a/Makefile.target b/Makefile.target
>> index 07af4d4..29287ed 100644
>> --- a/Makefile.target
>> +++ b/Makefile.target
>> @@ -27,12 +27,8 @@ ifdef CONFIG_USER_ONLY
>>   QEMU_PROG=qemu-$(TARGET_ARCH2)
>>   else
>>   # system emulator name
>> -ifeq ($(TARGET_ARCH), i386)
>> -QEMU_PROG=qemu$(EXESUF)
>> -else
>>   QEMU_PROG=qemu-system-$(TARGET_ARCH2)$(EXESUF)
>>   endif
>> -endif
>>
>>   PROGS=$(QEMU_PROG)
>>   STPFILES=
>> --
>> 1.7.4.1
>>
>>
>
>

  reply	other threads:[~2011-09-02 15:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-29 14:55 [Qemu-devel] [PATCH] Rename qemu -> qemu-system-i386 Anthony Liguori
2011-08-30 15:33 ` Juan Quintela
2011-08-30 15:41 ` Peter Maydell
2011-08-30 15:59   ` Anthony Liguori
2011-08-30 19:24 ` Blue Swirl
2011-09-02 15:39   ` Anthony Liguori [this message]
2011-09-03 11:46     ` Blue Swirl
2011-09-02 15:40 ` Anthony Liguori
2011-09-03 13:44   ` Andreas Färber
2011-09-03 16:11     ` Paolo Bonzini
2011-09-03 20:09     ` Anthony Liguori
2011-09-04 13:31       ` Andreas Färber

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=4E60F8CB.9080707@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=blauwirbel@gmail.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /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).