From: Jan Kiszka <jan.kiszka@web.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Avi Kivity <avi@redhat.com>,
kvm@vger.kernel.org, Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH] Rename KVM_UPSTREAM to OBSOLETE_KVM_IMPL
Date: Mon, 13 Sep 2010 21:03:19 +0200 [thread overview]
Message-ID: <4C8E7577.3020708@web.de> (raw)
In-Reply-To: <4C8E73F0.6030302@codemonkey.ws>
[-- Attachment #1: Type: text/plain, Size: 950 bytes --]
Am 13.09.2010 20:56, Anthony Liguori wrote:
> On 09/13/2010 01:52 PM, Jan Kiszka wrote:
>> Am 13.09.2010 19:54, Avi Kivity wrote:
>>
>>> The symbol KVM_UPSTREAM is used to mark sections of code that are
>>> part of
>>> the upstream kvm implemetation that is not used in qemu-kvm. However
>>> the
>>> name becomes ambiguous if qemu-kvm is merged upstream.
>>>
>> I doubt this is describing all cases correctly as well. Some changes
>> should rather happen the other way around (e.g. you surely don't want to
>> obsolete x86 kvm_arch_put/get_registers in favor of
>> kvm_arch_load/save_regs, do you?).
>>
>
> There's really no perfect name to describe what we're actually doing
> here. It's probably not a detail worth worrying that much about.
I don't mind the name as long as it doesn't reflect the strategy (but
why this change at all then?).
Jan (who would prefer to have the time for doing the cleanups)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2010-09-13 19:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 17:54 [PATCH] Rename KVM_UPSTREAM to OBSOLETE_KVM_IMPL Avi Kivity
2010-09-13 18:52 ` Jan Kiszka
2010-09-13 18:56 ` Anthony Liguori
2010-09-13 19:03 ` Jan Kiszka [this message]
2010-09-14 9:29 ` Avi Kivity
2010-09-14 10:42 ` Jan Kiszka
2010-09-14 10:50 ` Avi Kivity
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=4C8E7577.3020708@web.de \
--to=jan.kiszka@web.de \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@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