WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

RE: [Xen-ia64-devel] [PATCH 0/6] Add full evtchn mechanism forxen/ia64

To: "Isaku Yamahata" <yamahata@xxxxxxxxxxxxx>
Subject: RE: [Xen-ia64-devel] [PATCH 0/6] Add full evtchn mechanism forxen/ia64
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Mon, 22 May 2006 12:53:11 +0800
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 21 May 2006 21:53:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcZ9SBe0CXAU84noSCqdR4i9N+HPfwABRUwgAAMvoSA=
Thread-topic: [Xen-ia64-devel] [PATCH 0/6] Add full evtchn mechanism forxen/ia64
Hi, Isaku,
        Sorry for an empty mail slipped out. :-) And also sorry that I'm not 
very clear about the background of your suggestion. Why is serial 
required to be disabled in dom0? What's policy to choose which serial 
to be disabled, if there're multiple serial ports with different type?

        Previously there's some discussion about CONFIG_VT confliction, 
which seems to be hacked in xenlinux source directly now. Maybe I need 
to dig more to understand your question, since x86 also has 
CONFIG_XEN_DISABLE_SERIAL=y set.

        Basically speaking, this evtchn patch mainly changes the irq injection 
path. So if serial port needs to be disabled, that can be done w/ or w/o this 
patch either.  :-)

Thanks,
Kevin

>-----Original Message-----
>From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
>[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
>Tian, Kevin
>Sent: 2006年5月22日 11:15
>To: Isaku Yamahata
>Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>Subject: RE: [Xen-ia64-devel] [PATCH 0/6] Add full evtchn mechanism
>forxen/ia64
>
>>From: Isaku Yamahata [mailto:yamahata@xxxxxxxxxxxxx]
>>Sent: 2006年5月22日 10:33
>>
>>Hi Kevin.
>>
>>
>>On Thu, May 18, 2006 at 09:57:35PM +0800, Tian, Kevin wrote:
>>
>>>  45:        322        Phys-irq  serial
>>
>>It there any reason left to allow dom0 access to serial?
>>I gussed dom0 is allowed to access to serial because of external
>>interrupt.
>>This issue is resolved with your event channel patches.
>>So we can switch the default configs related to serial console.
>>I.e.
>>define CONFIG_XEN_CONSOLE_INPUT in
>>xen/include/asm-ia64/config.h
>>and
>>define CONFIG_XEN_DISABLE_SERIAL=y in xenLinux config
>>
>>--
>>yamahata
>
>_______________________________________________
>Xen-ia64-devel mailing list
>Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-ia64-devel

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel