linux-kernel - Re: [PATCH 16/25] xen: Use the hvc console infrastructure for Xen console

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <462E6222.3060302@goop.org>
Date:	Tue, 24 Apr 2007 13:01:38 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Olof Johansson <olof@...om.net>
CC:	Andi Kleen <ak@...e.de>, Andrew Morton <akpm@...ux-foundation.org>,
	virtualization@...ts.osdl.org, lkml <linux-kernel@...r.kernel.org>,
	Gerd Hoffmann <kraxel@...e.de>
Subject: Re: [PATCH 16/25] xen: Use the hvc console infrastructure for Xen
 console

Olof Johansson wrote:
> On Mon, Apr 23, 2007 at 02:56:54PM -0700, Jeremy Fitzhardinge wrote:
>   
>> Implement a Xen back-end for hvc console.
>>
>> From: Gerd Hoffmann <kraxel@...e.de>
>> Signed-off-by: Jeremy Fitzhardinge <jeremy@...source.com>
>>
>> ---
>>  arch/i386/xen/Kconfig     |    1 
>>  arch/i386/xen/events.c    |    3 -
>>  drivers/Makefile          |    3 +
>>  drivers/xen/Makefile      |    1 
>>  drivers/xen/hvc-console.c |  134 +++++++++++++++++++++++++++++++++++++++++++++
>>  include/xen/events.h      |    1 
>>  6 files changed, 142 insertions(+), 1 deletion(-)
>>     
>
> If you move the driver to drivers/char/hvc_xen.c instead, you won't have to do...
>
>   
>> +#include "../char/hvc_console.h"
>>     
>
> ...this.
>
> Other single-platform backend hvc drivers are under drivers/char already.

Good point.

    J
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/