From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Sasha Levin <levinsasha928@gmail.com>, penberg@kernel.org
Cc: mingo@elte.hu, asias.hejun@gmail.com, prasadjoshi124@gmail.com,
kvm@vger.kernel.org
Subject: Re: [PATCH 2/2] kvm tools: Modify ioport to use interval rbtree
Date: Sat, 21 May 2011 16:16:51 +0400 [thread overview]
Message-ID: <4DD7AD33.4020806@gmail.com> (raw)
In-Reply-To: <4DD7AB33.5080102@gmail.com>
On 05/21/2011 04:08 PM, Cyrill Gorcunov wrote:
> On 05/21/2011 02:55 PM, Sasha Levin wrote:
> ...
>>>> void ioport__register(u16 port, struct ioport_operations *ops, int count)
>>>> {
>>>> - int i;
>>>> + struct ioport_entry *entry;
>>>>
>>>> - for (i = 0; i < count; i++)
>>>> - ioport_ops[port + i] = ops;
>>>> + entry = ioport_search(&ioport_tree, port);
>>>> + if (entry)
>>>> + rb_int_erase(&ioport_tree, &entry->node);
>>>> +
>>>
>>> Hi Sasha, if I understand this correct we're simply drop old registartion, right? I think
>>> it should not be like that, if one port get used for several drivers/purposes we need a
>>> ref-counting, but at moment I think we simply should not allow to re-register port without
>>> previously unregister it. Or I miss something?
>>
>> Currently we register some ports as dummy ports in the ioport
>> initialization, and re-register them once they get someone who can use
>> them (for example, serial device).
>>
>> Not allowing ports to re-register would mean we can't reassign ports to
>> serial console when the serial console module gets loaded.
>>
>
> Yup, my bad, drop my complain, thanks ;)
>
What about this one on top? Pekka?
--
kvm tools: Print out a warning on io-port re-registration
We only support re-registartion of dummy io-port operations
so anything other should yield a warning and been considered
harmful until inspected and confirmed.
Signed-off-by: Cyrill Gorcunov <gorcunov@gmail.com>
---
Pekka, for some reason dropping the dummy io-ports for
serial console is not what I like. To be fair -- I can't
explain why, some gut feeling ;)
tools/kvm/ioport.c | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)
Index: linux-2.6.git/tools/kvm/ioport.c
===================================================================
--- linux-2.6.git.orig/tools/kvm/ioport.c
+++ linux-2.6.git/tools/kvm/ioport.c
@@ -72,8 +72,17 @@ void ioport__register(u16 port, struct i
struct ioport_entry *entry;
entry = ioport_search(&ioport_tree, port);
- if (entry)
+ if (entry) {
+ /*
+ * Only dummy io-port operations are supposed to be
+ * re-registered, anything other should be considered
+ * harmfull and issue warning until inspected and confirmed.
+ */
+ if (entry->ops != &dummy_read_write_ioport_ops &&
+ entry->ops != &dummy_write_only_ioport_ops)
+ pr_warning("Non-dummy ioport re-registered: %x", port);
rb_int_erase(&ioport_tree, &entry->node);
+ }
entry = malloc(sizeof(*entry));
if (entry == NULL)
prev parent reply other threads:[~2011-05-21 12:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-21 8:51 [PATCH 1/2] kvm tools: Fix rbtree-interval balancing Sasha Levin
2011-05-21 8:51 ` [PATCH 2/2] kvm tools: Modify ioport to use interval rbtree Sasha Levin
2011-05-21 10:31 ` Cyrill Gorcunov
2011-05-21 10:55 ` Sasha Levin
2011-05-21 12:08 ` Cyrill Gorcunov
2011-05-21 12:16 ` Cyrill Gorcunov [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=4DD7AD33.4020806@gmail.com \
--to=gorcunov@gmail.com \
--cc=asias.hejun@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=mingo@elte.hu \
--cc=penberg@kernel.org \
--cc=prasadjoshi124@gmail.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.