linux-kernel - Re: [PATCH] xen: setup pv irq ops vector earlier

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: <0362cb33-b6e6-a099-249f-b516b288f106@suse.com>
Date:   Wed, 11 Jul 2018 07:08:54 +0200
From:   Juergen Gross <jgross@...e.com>
To:     Boris Ostrovsky <boris.ostrovsky@...cle.com>,
        linux-kernel@...r.kernel.org, xen-devel@...ts.xenproject.org,
        x86@...nel.org
Cc:     hpa@...or.com, tglx@...utronix.de, mingo@...hat.com,
        stable@...r.kernel.org
Subject: Re: [PATCH] xen: setup pv irq ops vector earlier

On 11/07/18 00:26, Boris Ostrovsky wrote:
> On 07/02/2018 06:00 AM, Juergen Gross wrote:
>> Setting pv_irq_ops for Xen PV domains should be done as early as
>> possible in order to support e.g. very early printk() usage.
> 
> Will printk() work as result of this move? We still, for example,
> haven't set up console.

It will print to the kernel print buffer, so the output will be
available later.

> This will (probably) allow us not to crash (due to STI and such) but I
> am not sure "support" is the right term here.

Not crashing is big plus IMO. :-)


Juergen