All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Longpeng (Mike)" <longpeng2@huawei.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: rth@twiddle.net, pbonzini@redhat.com, mst@redhat.com,
	zhaoshenglong@huawei.com, arei.gonglei@huawei.com,
	peter.huangpeng@huawei.com, herongguang.he@huawei.com,
	qemu-devel@nongnu.org, "Longpeng(Mike)" <longpeng@huawei2.com>
Subject: Re: [Qemu-devel] [PATCH v3] target-i386: present virtual L3 cache info for vcpus
Date: Tue, 6 Sep 2016 08:31:31 +0800	[thread overview]
Message-ID: <57CE0E63.1090507@huawei.com> (raw)
In-Reply-To: <20160905185332.GN1151@thinpad.lan.raisama.net>

Hi Eduardo,

On 2016/9/6 2:53, Eduardo Habkost wrote:

> On Fri, Sep 02, 2016 at 10:22:55AM +0800, Longpeng(Mike) wrote:
> [...]
>> ---
>> Changes since v2:
>>   - add more useful commit mesage.
>>   - rename "compat-cache" to "l3-cache-shared".
> 
> What exactly "shared" means here? All the property does is to
> enable/disable the L3 cache, as its own description says:
> 
>>
>> +    /* Compatibility bits for old machine types.
>> +     * If true present virtual l3 cache for VM.
>> +     */
>> +    bool enable_l3_cache_shared;
>> +
> 
> Why not just "l3-cache" or "l3-cache-enabled"?
> 

I wanted to fix l1/l2's inconsistent bugs together originally, so I named it
"compat-cache". But later I thought it's too ugly to adding much l1/l2's
compatible macros, so I given up this idea. Instead, rename it to "l3-cache-shared".

Thanks for your good suggestion. I will choose "l3-cache-enabled" in the v5.

-- 
Regards,
Longpeng(Mike)

      reply	other threads:[~2016-09-06  0:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-02  2:22 [Qemu-devel] [PATCH v3] target-i386: present virtual L3 cache info for vcpus Longpeng(Mike)
2016-09-02  2:41 ` Gonglei (Arei)
2016-09-02 22:52 ` Michael S. Tsirkin
2016-09-05  1:16   ` Longpeng (Mike)
2016-09-05 18:53 ` Eduardo Habkost
2016-09-06  0:31   ` Longpeng (Mike) [this message]

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=57CE0E63.1090507@huawei.com \
    --to=longpeng2@huawei.com \
    --cc=arei.gonglei@huawei.com \
    --cc=ehabkost@redhat.com \
    --cc=herongguang.he@huawei.com \
    --cc=longpeng@huawei2.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.huangpeng@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=zhaoshenglong@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.