From: Jan Kiszka <jan.kiszka@web.de>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [uq/master patch 2/5] kvm: add logging count to slots
Date: Sun, 25 Apr 2010 17:07:02 +0200 [thread overview]
Message-ID: <4BD45A96.3080800@web.de> (raw)
In-Reply-To: <4BD458AD.9020500@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]
Avi Kivity wrote:
> On 04/25/2010 05:51 PM, Jan Kiszka wrote:
>> Avi Kivity wrote:
>>
>>> On 04/25/2010 05:29 PM, Jan Kiszka wrote:
>>>
>>>>
>>>>> There isn't. But I don't like hidden breakage.
>>>>>
>>>>>
>>>> It's (so far) an unproblematic API property we can document. I don't
>>>> like changing APIs just for "there might be the case that...".
>>>>
>>>>
>>> I guess it's one of those agree to disagree things. I dislike known
>>> broken APIs even if their none of their users are affected.
>>>
>> The API is not broken. I intentionally designed it for the single user
>> as I saw no need for more. If I oversaw something, I would really like
>> to learn about these cases.
>>
>
> The fact that the API assumes a single user is what's broken IMO.
>
> If the API were to take a memory slot as parameter you could say it is
> the responsibility of the slot's owner to multiplex (and since vga has a
> single owner, no need to multiplex). But it takes a range.
No, the API accepts only a single slot. If you try passing bogus ranges
that span multiple or incomplete slots, you get what you deserve - a bug
message.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@web.de>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: [uq/master patch 2/5] kvm: add logging count to slots
Date: Sun, 25 Apr 2010 17:07:02 +0200 [thread overview]
Message-ID: <4BD45A96.3080800@web.de> (raw)
In-Reply-To: <4BD458AD.9020500@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]
Avi Kivity wrote:
> On 04/25/2010 05:51 PM, Jan Kiszka wrote:
>> Avi Kivity wrote:
>>
>>> On 04/25/2010 05:29 PM, Jan Kiszka wrote:
>>>
>>>>
>>>>> There isn't. But I don't like hidden breakage.
>>>>>
>>>>>
>>>> It's (so far) an unproblematic API property we can document. I don't
>>>> like changing APIs just for "there might be the case that...".
>>>>
>>>>
>>> I guess it's one of those agree to disagree things. I dislike known
>>> broken APIs even if their none of their users are affected.
>>>
>> The API is not broken. I intentionally designed it for the single user
>> as I saw no need for more. If I oversaw something, I would really like
>> to learn about these cases.
>>
>
> The fact that the API assumes a single user is what's broken IMO.
>
> If the API were to take a memory slot as parameter you could say it is
> the responsibility of the slot's owner to multiplex (and since vga has a
> single owner, no need to multiplex). But it takes a range.
No, the API accepts only a single slot. If you try passing bogus ranges
that span multiple or incomplete slots, you get what you deserve - a bug
message.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2010-04-25 15:07 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 17:04 [uq/master patch 0/5] prepare for qemu-kvm's usage of upstream memslot code Marcelo Tosatti
2010-04-23 17:04 ` [Qemu-devel] " Marcelo Tosatti
2010-04-23 17:04 ` [uq/master patch 1/5] vga: fix typo in length passed to kvm_log_stop Marcelo Tosatti
2010-04-23 17:04 ` [Qemu-devel] " Marcelo Tosatti
2010-04-23 17:04 ` [uq/master patch 2/5] kvm: add logging count to slots Marcelo Tosatti
2010-04-23 17:04 ` [Qemu-devel] " Marcelo Tosatti
2010-04-24 7:34 ` Jan Kiszka
2010-04-24 7:34 ` [Qemu-devel] " Jan Kiszka
2010-04-25 12:33 ` Avi Kivity
2010-04-25 12:33 ` [Qemu-devel] " Avi Kivity
2010-04-25 13:57 ` Jan Kiszka
2010-04-25 13:57 ` [Qemu-devel] " Jan Kiszka
2010-04-25 14:17 ` Avi Kivity
2010-04-25 14:17 ` [Qemu-devel] " Avi Kivity
2010-04-25 14:29 ` Jan Kiszka
2010-04-25 14:29 ` [Qemu-devel] " Jan Kiszka
2010-04-25 14:41 ` Avi Kivity
2010-04-25 14:41 ` [Qemu-devel] " Avi Kivity
2010-04-25 14:51 ` Jan Kiszka
2010-04-25 14:51 ` [Qemu-devel] " Jan Kiszka
2010-04-25 14:58 ` Avi Kivity
2010-04-25 14:58 ` [Qemu-devel] " Avi Kivity
2010-04-25 15:07 ` Jan Kiszka [this message]
2010-04-25 15:07 ` Jan Kiszka
2010-04-25 15:22 ` Avi Kivity
2010-04-25 15:22 ` [Qemu-devel] " Avi Kivity
2010-04-25 16:42 ` Jan Kiszka
2010-04-25 16:42 ` [Qemu-devel] " Jan Kiszka
2010-04-26 5:37 ` Avi Kivity
2010-04-26 5:37 ` [Qemu-devel] " Avi Kivity
2010-04-26 13:47 ` Marcelo Tosatti
2010-04-26 13:47 ` [Qemu-devel] " Marcelo Tosatti
2010-04-23 17:04 ` [uq/master patch 3/5] introduce leul_to_cpu Marcelo Tosatti
2010-04-23 17:04 ` [Qemu-devel] " Marcelo Tosatti
2010-04-23 17:04 ` [uq/master patch 4/5] kvm: port qemu-kvm's bitmap scanning Marcelo Tosatti
2010-04-23 17:04 ` [Qemu-devel] " Marcelo Tosatti
2010-04-23 17:04 ` [uq/master patch 5/5] introduce qemu_ram_map Marcelo Tosatti
2010-04-23 17:04 ` [Qemu-devel] " Marcelo Tosatti
2010-04-25 12:33 ` [uq/master patch 0/5] prepare for qemu-kvm's usage of upstream memslot code Avi Kivity
2010-04-25 12:33 ` [Qemu-devel] " 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=4BD45A96.3080800@web.de \
--to=jan.kiszka@web.de \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--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 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.