|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] current not very current (vs curr_vcpu)
On 24/02/2010 03:55, "Mukesh Rathor" <mukesh.rathor@xxxxxxxxxx> wrote:
>> Given the only thing this apparently affected was some of your own
>> ad-hoc debug code, do we really care about this at all? We can
>> probably happily just leave it.
>
> Well, I'm afraid not. It breaks the debug code to debug the hang. More
> importantly, it also breaks my debuggers, which some people from outside
> oracle are also using. Most of our new high end servers are accessed
> via virtual serial port, so if ns16550_poll() call is related to it,
> then it'll only get worse. Moreover, anybody reading and copying that
> code to do something similar will be misled.
Okay, see how xen-unstable:20969 works for you.
-- Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] current not very current (vs curr_vcpu), Mukesh Rathor
- Re: [Xen-devel] current not very current (vs curr_vcpu), Keir Fraser
- Re: [Xen-devel] current not very current (vs curr_vcpu), Mukesh Rathor
- Re: [Xen-devel] current not very current (vs curr_vcpu), Keir Fraser
- Re: [Xen-devel] current not very current (vs curr_vcpu), Mukesh Rathor
- Re: [Xen-devel] current not very current (vs curr_vcpu), Keir Fraser
- Re: [Xen-devel] current not very current (vs curr_vcpu), Mukesh Rathor
- Re: [Xen-devel] current not very current (vs curr_vcpu), Mukesh Rathor
- Re: [Xen-devel] current not very current (vs curr_vcpu), Keir Fraser
- Re: [Xen-devel] current not very current (vs curr_vcpu), Mukesh Rathor
- Re: [Xen-devel] current not very current (vs curr_vcpu),
Keir Fraser <=
- Re: [Xen-devel] current not very current (vs curr_vcpu), Mukesh Rathor
- Re: [Xen-devel] current not very current (vs curr_vcpu), Keir Fraser
|
|
|
|
|