linux-kernel - Re: [PATCH 0/5] add bus driver for Unisys s-Par paravirtualized devices to arch/x86

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: <20160517135133.GC18227@kroah.com>
Date:	Tue, 17 May 2016 06:51:33 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	David Kershner <david.kershner@...sys.com>
Cc:	corbet@....net, tglx@...utronix.de, mingo@...hat.com,
	hpa@...or.com, erik.arfvidson@...sys.com, timothy.sell@...sys.com,
	hofrat@...dl.org, dzickus@...hat.com, jes.sorensen@...hat.com,
	alexander.curtin@...sys.com, janani.rvchndrn@...il.com,
	sudipm.mukherjee@...il.com, prarit@...hat.com,
	david.binder@...sys.com, nhorman@...hat.com,
	dan.j.williams@...el.com, linux-kernel@...r.kernel.org,
	linux-doc@...r.kernel.org, driverdev-devel@...uxdriverproject.org,
	sparmaintainer@...sys.com
Subject: Re: [PATCH 0/5] add bus driver for Unisys s-Par paravirtualized
 devices to arch/x86

On Tue, May 17, 2016 at 03:27:56AM -0400, David Kershner wrote:
> This patchset moves the visorbus driver (fromdrivers/staging/unisys/visorbus)
> and its dependent headers files (from drivers/staging/unisys/include)
> out of staging into the main kernel tree.
> 
> The visorbus driver is a bus driver for various paravirtualized devices
> presented within a Unisys s-Par guest environment.  Drivers for these
> devices are also currently present under drivers/staging/unisys/, which we
> intend to also move out of staging immediately after visorbus.  All of
> these other drivers are dependent upon visorbus and the include directory,
> which is why we would like to move these first.
> 
> Our initial consultations with various members of the community have led us
> to the conclusion that the most appropriate locations for these is:
>     arch/x86/visorbus/       (driver)
>     include/linux/visorbus/  (header files)
> 
> The rationale is that visorbus is dependent on x86-64 architecture.

What makes it dependent on x86?  What prevents it from running on some
other architecture (not the fact that no one has made such hardware,
just the code reasons please.)

And given that this is the middle of the merge window, no maintainer is
going to have any time to do anything with these, can you please resend
them after 4.7-rc1 is out?

thanks,

greg k-h