Re: [PATCH 1/3 v19] sys_membarrier(): system-wide memory barrier (generic, x86)

Hi Mathieu, In the patch below you have a man page type of text. Is that just plain text, or do you have some groff source somewhere? Thanks, Michael On 07/10/2015 10:58 PM, Mathieu Desnoyers wrote: > Here is an implementation of a new system call, sys_membarrier(), which > executes a memory

Re: [PATCH v3] capabilities.7, prctl.2: Document ambient capabilities

Hi Andy, I have applied your patch (below). Thanks for writing it. But I have a question or two and a request. === In the capabilities(7) page tehre is the longstanding text: An application can use the following call to lock itself, and all of its descendants, into an

[PATCH v6 1/4] firmware: introduce sysfs driver for QEMU's fw_cfg device

From: Gabriel Somlo Make fw_cfg entries of type "file" available via sysfs. Entries are listed under /sys/firmware/qemu_fw_cfg/by_key, in folders named after each entry's selector key. Filename, selector value, and size read-only attributes are included for each entry. Also, a

[PATCH v6 0/4] SysFS driver for QEMU fw_cfg device

Allow access to QEMU firmware blobs, passed into the guest VM via the fw_cfg device, through SysFS entries. Blob meta-data (e.g. name, size, and fw_cfg key), as well as the raw binary blob data may be accessed. The SysFS access location is /sys/firmware/qemu_fw_cfg/... and was selected based on

[PATCH v6 4/4] devicetree: update documentation for fw_cfg ARM bindings

From: Gabriel Somlo Remove fw_cfg hardware interface details from Documentation/devicetree/bindings/arm/fw-cfg.txt, and replace them with a pointer to the authoritative documentation in the QEMU source tree. Signed-off-by: Gabriel Somlo Cc: Laszlo Ersek

[PATCH v6 3/4] firmware: create directory hierarchy for sysfs fw_cfg entries

From: Gabriel Somlo Each fw_cfg entry of type "file" has an associated 56-char, nul-terminated ASCII string which represents its name. While the fw_cfg device doesn't itself impose any specific naming convention, QEMU developers have traditionally used path name semantics (i.e.

[PATCH v6 2/4] kobject: export kset_find_obj() for module use

From: Gabriel Somlo Signed-off-by: Gabriel Somlo --- lib/kobject.c | 1 + 1 file changed, 1 insertion(+) diff --git a/lib/kobject.c b/lib/kobject.c index 7cbccd2..90d1be6 100644 --- a/lib/kobject.c +++ b/lib/kobject.c @@ -861,6 +861,7 @@ struct kobject

Re: [PATCH 01/23] userfaultfd: linux/Documentation/vm/userfaultfd.txt

Hi Andrea, On 09/11/2015 10:47 AM, Michael Kerrisk (man-pages) wrote: > On 05/14/2015 07:30 PM, Andrea Arcangeli wrote: >> Add documentation. > > Hi Andrea, > > I do not recall... Did you write a man page also for this new system call? No response to my last mail, so I'll try again... Did you

[PATCH 3/4] drm, ipu-v3: use https://linuxtv.org for LinuxTV URL

While https was always supported on linuxtv.org, only in Dec 3 2015 the website is using valid certificates. As we're planning to drop pure http support on some future, change the references at DRM include and at the ipu-v3 driver to point to the https://linuxtv.org URL instead. Signed-off-by:

Re: [RFC PATCH V2 0/3] IXGBE/VFIO: Add live migration support for SRIOV NIC

On 12/04/2015 08:32 AM, Lan, Tianyu wrote: Hi Michael & Alexander: Thanks a lot for your comments and suggestions. We still need to support Windows guest for migration and this is why our patches keep all changes in the driver since it's impossible to change Windows kernel. That is a poor

Re: [PATCH 01/23] userfaultfd: linux/Documentation/vm/userfaultfd.txt

Hello Michael, On Fri, Dec 04, 2015 at 04:50:03PM +0100, Michael Kerrisk (man-pages) wrote: > Hi Andrea, > > On 09/11/2015 10:47 AM, Michael Kerrisk (man-pages) wrote: > > On 05/14/2015 07:30 PM, Andrea Arcangeli wrote: > >> Add documentation. > > > > Hi Andrea, > > > > I do not recall... Did

Re: [RFC PATCH V2 0/3] IXGBE/VFIO: Add live migration support for SRIOV NIC

Hi Michael & Alexander: Thanks a lot for your comments and suggestions. We still need to support Windows guest for migration and this is why our patches keep all changes in the driver since it's impossible to change Windows kernel. Following is my idea to do DMA tracking. Inject event to VF

Re: [PATCH v3] capabilities.7, prctl.2: Document ambient capabilities

On Fri, Dec 4, 2015 at 7:08 AM, Michael Kerrisk (man-pages) wrote: > Hi Andy, > > I have applied your patch (below). Thanks for writing it. > But I have a question or two and a request. > > === > > In the capabilities(7) page tehre is the longstanding text: > >An

Re: [PATCH 3/4] drm, ipu-v3: use https://linuxtv.org for LinuxTV URL

Am Freitag, den 04.12.2015, 10:46 -0200 schrieb Mauro Carvalho Chehab: > While https was always supported on linuxtv.org, only in > Dec 3 2015 the website is using valid certificates. > > As we're planning to drop pure http support on some > future, change the references at DRM include and at >

Re: [PATCH RFC] Introduce new security.nscapability xattr

Quoting Eric W. Biederman (ebied...@xmission.com): > "Serge E. Hallyn" writes: > > > A common way for daemons to run with minimal privilege is to start as root, > > perhaps setuid-root, choose a desired capability set, set PR_SET_KEEPCAPS, > > then change uid to

Re: [PATCH 00/34] x86: Memory Protection Keys (v5)

On Thu, Dec 3, 2015 at 5:14 PM, Dave Hansen wrote: > Memory Protection Keys for User pages is a CPU feature which will > first appear on Skylake Servers, but will also be supported on > future non-server parts. It provides a mechanism for enforcing > page-based protections, but

Re: [PATCH 00/34] x86: Memory Protection Keys (v5)

On 12/04/2015 03:31 PM, Andy Lutomirski wrote: > On Thu, Dec 3, 2015 at 5:14 PM, Dave Hansen wrote: >> Memory Protection Keys for User pages is a CPU feature which will >> first appear on Skylake Servers, but will also be supported on >> future non-server parts. It provides a

Re: [PATCH 26/34] mm: implement new mprotect_key() system call

Dave, On 12/04/2015 02:15 AM, Dave Hansen wrote: > From: Dave Hansen > > mprotect_key() is just like mprotect, except it also takes a > protection key as an argument. On systems that do not support > protection keys, it still works, but requires that key=0. >