The Guest Information Area (GIB) and its mechanics is part of
the AIV facility. It provides hardware support to process
Adapter Interruptions (AI) for pagable storage mode guests.
Whenever a guest cannot process an AI because none of its
vcpus is running in SIE context, a GIB alert interruption
On Wed, 2018-12-19 at 20:55 +0200, Igor Stoppa wrote:
> The checkpatch.pl script complains when the help section of a Kconfig
> entry is too short, but it doesn't really explain what it is looking
> for. Instead, it gives a generic warning that one should consider writing
> a paragraph.
>
> But
Make sure the debug feature and its allocated resources get
released upon unsuccessful architecture initialization.
A related indication of the issue will be reported as kernel
message.
Signed-off-by: Michael Mueller
Reviewed-by: Cornelia Huck
Reviewed-by: Pierre Morel
Reviewed-by: David
This will shorten the length of code lines.
All GISA related static inline functions are local to interrupt.c
Signed-off-by: Michael Mueller
---
arch/s390/kvm/interrupt.c | 26 +-
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a/arch/s390/kvm/interrupt.c
The change hepls to reduce line length and
icreases code readability.
Signed-off-by: Michael Mueller
---
arch/s390/kvm/interrupt.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/arch/s390/kvm/interrupt.c b/arch/s390/kvm/interrupt.c
index
Add the IAM (Interruption Alert Mask) to the architecture specific
kvm struct. This mask in the GISA is used to define for which ISC
a GIB alert can be issued.
The functions kvm_s390_gisc_register() and kvm_s390_gisc_unregister()
are used to (un)register a GISC (guest ISC) with a virtual machine
The patch implements a handler for GIB alert interruptions
on the host. Its task is to alert guests that interrupts are
pending for them.
A GIB alert interrupt statistic counter is added as well:
$ cat /proc/interrupts
CPU0 CPU1
...
GAL: 23 37 [I/O] GIB Alert
By initializing the GIB, it will be used by the kvm host.
Signed-off-by: Michael Mueller
---
arch/s390/kvm/kvm-s390.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/arch/s390/kvm/kvm-s390.c b/arch/s390/kvm/kvm-s390.c
index 2d10e175862c..777c8a87d81c 100644
---
The patch adds the parameter irq_flags and allows to
restore the Interruption Alert Mask (IAM) in the GISA
atomically while guaranteeing the IPM is clean.
The function returns the IPM of the GISA. If the returned
value is 0x00 and the IRQ_FLAG_IAM was set, the IAM has
been restored.
New irq
This function processes the Gib Alert List (GAL). It is required
to run when either a gib alert interruption has been received or
a gisa that is in the alert list is cleared or dropped.
The GAL is build up by millicode, when the respective ISC bit is
set in the Interruption Alert Mask (IAM) and
The IAM shall no be restored when deliverable interruptions are
delivered to vcpus by means of the PSW swap mechanism. That would
trigger the GIB alert millicode although we know that SIE will be
able to handle the pending interruption on entry.
Signed-off-by: Michael Mueller
---
Adding the kvm reference to struct sie_page2 will allow to
determine the kvm a given gisa belongs to:
container_of(gisa, struct sie_page2, gisa)->kvm
This functionality will be required to process a gisa in
gib alert interruption context.
Signed-off-by: Michael Mueller
Reviewed-by: Pierre
This patch implements the Set Guest Information Block operation
to request association or disassociation of a Guest Information
Block (GIB) with the Adapter Interruption Facility. The operation
is required to receive GIB alert interrupts for guest adapters
in conjunction with AIV and GISA.
The Guest Information Block (GIB) links the GISA of all guests
that have adapter interrupts pending. These interrupts cannot be
delivered because no vcpu of these guests is currently running in
SIE context. Instead, a GIB alert is issued on the host to schedule
these guests to run.
This mechanism
Use a single function with parameter irq_flags to differentiate
between cases.
New irq flag:
IRQ_FLAG_LOCAL: include vcpu local interruptions pending
IRQ_FLAG_FLOATING: include vcpu floating interruptions pending
IRQ_FLAG_GISA: include GISA interruptions pending in IPM
New irq masks:
Interruption types that are not represented in GISA shall
use pending_irqs_no_gisa() to test pending interruptions.
Signed-off-by: Michael Mueller
---
arch/s390/kvm/interrupt.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/s390/kvm/interrupt.c
Hi Marcel,
thanks for the review!
On Wed, Dec 19, 2018 at 03:22:12PM +0100, Marcel Holtmann wrote:
> > Add HCI_QUIRK_USE_BDADDR_PROPERTY to allow controllers to retrieve
> > the public Bluetooth address from the firmware node property
> > 'local-bd-address'. If quirk is set and the property
The remove_memory_block() function was renamed to in commit
cc292b0b4302 ("drivers/base/memory.c: rename remove_memory_block() to
remove_memory_section()").
Signed-off-by: Dan Carpenter
---
drivers/base/memory.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
This function will be used by the GISA init and the GISA
clear operation. Thus it gets factored out here.
Signed-off-by: Michael Mueller
Reviewed-by: Pierre Morel
Reviewed-by: Janosch Frank
Reviewed-by: Cornelia Huck
Reviewed-by: David Hildenbrand
---
arch/s390/kvm/interrupt.c | 11
I'm announcing the release of the 4.19.11 kernel.
All users of the 4.19 kernel series must upgrade.
The updated 4.19.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.19.y
and can be browsed at the normal kernel.org git web
diff --git a/Makefile b/Makefile
index 36d9de42def3..676155d4dc3e 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 4
PATCHLEVEL = 19
-SUBLEVEL = 10
+SUBLEVEL = 11
EXTRAVERSION =
NAME = "People's Front"
diff --git
On Wed, Dec 19, 2018 at 05:19:22PM +0200, Alexander Shishkin wrote:
> The 'nr_pages' attribute of the 'msc' subdevices parses a comma-separated
> list of window sizes, passed from userspace. However, there is a bug in
> the string parsing logic wherein it doesn't exclude the comma character
> from
On Wed, Dec 19, 2018 at 01:19:53PM +1100, Dave Chinner wrote:
> Putting metadata in user files beyond EOF doesn't work with XFS's
> post-EOF speculative allocation algorithms.
>
> i.e. Filesystem design/algorithms often assume that the region
> beyond EOF in user files is a write-only region.
Hi!
> +static DEVICE_ATTR_WO(ctrl_bank_a_mix);
> +static DEVICE_ATTR_WO(ctrl_bank_b_mix);
> +static DEVICE_ATTR_WO(ctrl_bank_c_mix);
> +
> +static struct attribute *lp5024_ctrl_bank_attrs[] = {
> + _attr_ctrl_bank_a_mix.attr,
> + _attr_ctrl_bank_b_mix.attr,
> +
On Wed, Dec 19, 2018 at 02:34:44PM +0100, Juri Lelli wrote:
> Commit fc560a26acce ("cpuset: replace cpuset->stack_list with
> cpuset_for_each_descendant_pre()") removed the local list (q)
> that was used to perform a top-down scan of all cpusets;
> however, comments mentioning it were not updated.
On Wed, Dec 19, 2018 at 02:09:50PM -0500, Waiman Long wrote:
> With the default SPEC_STORE_BYPASS_SECCOMP/SPEC_STORE_BYPASS_PRCTL mode,
> the TIF_SSBD bit will be inherited when a new task is fork'ed or cloned.
>
> As only certain class of applications (like Java) requires disabling
> speculative
>"expecting a 'help' section of
> $min_conf_desc_length or more lines\n" . $herecurr);
> or maybe
>"please write a paragraph that describes
> the config symbol fully ($min_conf_desc_length or more lines)\n" . $herecurr);
>
On Tue, 18 Dec 2018 14:33:21 -0600
Tom Zanussi wrote:
> From: Tom Zanussi
>
> There's no need to use strlen() for static strings when the length is
> already known, so update trace_events_hist.c with sizeof() for those
> cases.
>
> Signed-off-by: Tom Zanussi
> ---
>
Pavel
Thanks for the review.
On 12/19/2018 01:34 PM, Pavel Machek wrote:
> Hi!
>
>> +static DEVICE_ATTR_WO(ctrl_bank_a_mix);
>> +static DEVICE_ATTR_WO(ctrl_bank_b_mix);
>> +static DEVICE_ATTR_WO(ctrl_bank_c_mix);
>> +
>> +static struct attribute *lp5024_ctrl_bank_attrs[] = {
>> +
On 19.12.2018 16:32, Chris Chiu wrote:
> On Wed, Dec 19, 2018 at 4:28 AM Heiner Kallweit wrote:
>>
>> On 18.12.2018 14:25, Chris Chiu wrote:
>>> On Tue, Dec 18, 2018 at 3:08 AM Heiner Kallweit
>>> wrote:
On 17.12.2018 14:25, Chris Chiu wrote:
> On Fri, Dec 14, 2018 at 3:37 PM
On 12/19/2018 02:38 PM, Andi Kleen wrote:
> On Wed, Dec 19, 2018 at 02:09:50PM -0500, Waiman Long wrote:
>> With the default SPEC_STORE_BYPASS_SECCOMP/SPEC_STORE_BYPASS_PRCTL mode,
>> the TIF_SSBD bit will be inherited when a new task is fork'ed or cloned.
>>
>> As only certain class of
Hi Steve,
On Wed, 2018-12-19 at 14:40 -0500, Steven Rostedt wrote:
> On Tue, 18 Dec 2018 14:33:21 -0600
> Tom Zanussi wrote:
>
> > From: Tom Zanussi
> >
> > There's no need to use strlen() for static strings when the length
> > is
> > already known, so update trace_events_hist.c with sizeof()
Dmitry Vyukov wrote:
> On Wed, Dec 19, 2018 at 7:37 PM syzbot
> wrote:
> >
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:a26d94bff4d5 net: bridge: remove unneeded variable 'err'
> > git tree: net-next
> > console output:
In the 4.19 kernel, we are seeing a USERCOPY_WARN in __copy_to_user
during bootup.
The code-flow is something like this:
(arch/arm64/kernel/signal.c)
struct sigset_t *set;
__copy_to_user(>uc.uc_sigmask, set, sizeof(*set))
(include/linux/uaccess.h)
__copy_to_user(void __user *to, const void
msm8998 has a dozen i2c controllers which can be used to connect to board
specific peripherals. Enumerate the controllers so that boards can wire
up as needed.
Signed-off-by: Jeffrey Hugo
---
arch/arm64/boot/dts/qcom/msm8998.dtsi | 180 ++
1 file changed, 180
From: Dave Hansen
I frequently find myself contemplating my life choices as I try to
find 3-character entries in the 1,000-character, unsorted "flags:"
field of /proc/cpuinfo.
Sort that field, giving me hours back in my day.
This eats up ~1200 bytes (NCAPINTS*2*32) of space for the sorted
On 18 Dec 2018, at 13:57, Jens Axboe wrote:
> On 12/18/18 2:11 AM, kemi wrote:
>> Hi, All
>> Do we have special reason to keep this patch (316ba5736c9:brd: Mark
>> as non-rotational).
>> which leads to a performance regression when BRD is used as a disk on
>> btrfs.
>
> I really suspect that
Hi Shawn,
On Tue, Nov 27, 2018 at 06:07:22PM +0800, Shawn Guo wrote:
> It adds Synopsys 28nm Femto High-Speed USB PHY driver support, which
> is usually paired with Synopsys DWC3 USB controllers on Qualcomm SoCs.
>
> Signed-off-by: Shawn Guo
> ---
> drivers/phy/qualcomm/Kconfig
On Wed, 19 Dec 2018 20:17:42 +0100
Michael Mueller wrote:
> Make sure the debug feature and its allocated resources get
> released upon unsuccessful architecture initialization.
>
> A related indication of the issue will be reported as kernel
> message.
>
> Signed-off-by: Michael Mueller
>
On Wed 2018-12-19 13:41:18, Dan Murphy wrote:
> Pavel
>
> Thanks for the review.
>
> On 12/19/2018 01:34 PM, Pavel Machek wrote:
> > Hi!
> >
> >> +static DEVICE_ATTR_WO(ctrl_bank_a_mix);
> >> +static DEVICE_ATTR_WO(ctrl_bank_b_mix);
> >> +static DEVICE_ATTR_WO(ctrl_bank_c_mix);
> >> +
> >>
Hi Song,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on bpf-next/master]
url:
https://github.com/0day-ci/linux/commits/Song-Liu/perf-bpf-Introduce-PERF_RECORD_KSYMBOL/20181220-023635
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git
On Wed, 19 Dec 2018 20:17:43 +0100
Michael Mueller wrote:
> The change hepls to reduce line length and
s/hepls/helps/
> icreases code readability.
s/icreases/increases/
>
> Signed-off-by: Michael Mueller
> ---
> arch/s390/kvm/interrupt.c | 20 ++--
> 1 file changed, 10
On Wed, 2018-12-19 at 13:46 -0600, Tom Zanussi wrote:
> Hi Steve,
>
> On Wed, 2018-12-19 at 14:40 -0500, Steven Rostedt wrote:
> > On Tue, 18 Dec 2018 14:33:21 -0600
> > Tom Zanussi wrote:
> >
> > > From: Tom Zanussi
> > >
> > > There's no need to use strlen() for static strings when the
> >
On Wed, 19 Dec 2018 20:17:45 +0100
Michael Mueller wrote:
> Interruption types that are not represented in GISA shall
> use pending_irqs_no_gisa() to test pending interruptions.
>
> Signed-off-by: Michael Mueller
> ---
> arch/s390/kvm/interrupt.c | 4 ++--
> 1 file changed, 2 insertions(+), 2
On Wed, 2018-12-19 at 13:46 -0600, Tom Zanussi wrote:
> Hi Steve,
>
> On Wed, 2018-12-19 at 14:40 -0500, Steven Rostedt wrote:
> > On Tue, 18 Dec 2018 14:33:21 -0600
> > Tom Zanussi wrote:
> >
> > > From: Tom Zanussi
> > >
> > > There's no need to use strlen() for static strings when the
On Wed, 2018-12-19 at 14:16 -0600, Tom Zanussi wrote:
>
> How's this?
>
> [PATCH] tracing: Introduce and use strcmp_const() for hist triggers
>
> Provide a new strcmp_const() macro and make use of it instead of the
> longer and more error-prone strncmp(str, "str", sizeof("str") - 1).
[]
> diff
On Tue, Dec 18, 2018 at 2:46 AM Rafael J. Wysocki wrote:
>
> On Monday, December 17, 2018 5:32:10 PM CET Dan Williams wrote:
> > On Mon, Dec 17, 2018 at 2:12 AM Rafael J. Wysocki
> > wrote:
> > >
> > > On Saturday, December 15, 2018 2:48:30 AM CET Dan Williams wrote:
> > > > Changes since v4:
On Wed, 19 Dec 2018 13:46:49 -0600
Tom Zanussi wrote:
> Yeah, I had considered it but wasn't sure it was worth it. Since
> you're suggesting it is, I can send another patch on top of these, or
> feel free if you want to too. ;-)
>
Here, want to ack/review it?
-- Steve
>From
On Wed, 19 Dec 2018 14:16:31 -0600
Tom Zanussi wrote:
> > Yeah, I had considered it but wasn't sure it was worth it. Since
> > you're suggesting it is, I can send another patch on top of these, or
> > feel free if you want to too. ;-)
> >
>
> How's this?
>
> [PATCH] tracing: Introduce
On Wed, 19 Dec 2018 12:20:19 -0800
Joe Perches wrote:
> > Yeah, I had considered it but wasn't sure it was worth it. Since
> > you're suggesting it is, I can send another patch on top of these, or
> > feel free if you want to too. ;-)
>
> I believe the 'strlen("foo") -> sizeof("foo") - 1'
>
On 19/12/18 05:12, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the kvm tree got a conflict in:
>
> arch/x86/kvm/x86.c
>
> between commit:
>
> eb012ef3b4e3 ("x86: Remove Intel MPX")
>
> from the tip tree and commit:
>
> b666a4b69739 ("kvm: x86: Dynamically allocate
On Mon 17-12-18 20:23:23, Dan Williams wrote:
> Andrew, this needs at least an ack from Michal, or Mel before it moves
> forward. It would be a nice surprise / present to see it move forward
> before the holidays, but I suspect it may need to simmer until the new
> year. This series is against
On Wed, 19 Dec 2018 12:22:38 -0800
Joe Perches wrote:
> On Wed, 2018-12-19 at 14:16 -0600, Tom Zanussi wrote:
> >
> > How's this?
> >
> > [PATCH] tracing: Introduce and use strcmp_const() for hist triggers
> >
> > Provide a new strcmp_const() macro and make use of it instead of the
> > longer
If a serial console write occured while a UART transmit command was
waiting for a done signal then no further data would be sent until
something new kicked the system into gear. If there is already data
waiting in the circular buffer we must re-enable the tx watermark so we
receive the expected
On Wed, Dec 19, 2018 at 11:57 AM Clément VUCHENER
wrote:
>
> Le sam. 15 déc. 2018 à 15:45, Clément VUCHENER
> a écrit :
> >
> > Le ven. 14 déc. 2018 à 19:37, Harry Cutts a écrit :
> > >
> > > Hi Clement,
> > >
> > > On Fri, 14 Dec 2018 at 05:47, Clément VUCHENER
> > > wrote:
> > > > Hi, The
Hi Robin,
Thanks for the feedback :)
>The whole point of the library idea was to factor out the code in such a way
>that all the details
>specific to a particular implementation can be kept together. But what this
>patch does is insert
>Tegra194-specific handling all through the 'common' code,
On Wed, 5 Dec 2018 17:03:25 +0200, Roger Quadros wrote:
> Add support for USB2 PHY on AM654x SoC.
>
> Signed-off-by: Roger Quadros
> Signed-off-by: Sekhar Nori
> ---
> Documentation/devicetree/bindings/phy/ti-phy.txt | 1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: Rob Herring
On Wed, 5 Dec 2018 16:47:50 +0100, =?UTF-8?q?Pawe=C5=82=20Chmiel?= wrote:
> Add information about new reset-gpios property to driver documentation
>
> Signed-off-by: Paweł Chmiel
> ---
> Documentation/devicetree/bindings/media/si470x.txt | 2 ++
> 1 file changed, 2 insertions(+)
>
eMMC-5.1 JESD84-B51 Spec (Section 6.6.39.1), mentions "Prior to
enabling command queuing, the block size shall be set to 512 B.
Device may respond with an error to CMD46/CMD47 if block size
is not 512 B".
This patch fixes the sequence to follow exact as per the spec.
Signed-off-by: Sowjanya
As per eMMC5.1 Spec Section 6.6.39.1, DMA Block size should be to 512 B
before enabling command queue.
Tegra SDHCI Host design strictly follows this sequence preventing write
access to SDHCI_BLOCK_SIZE when CQE is set in CQHCI_CFG. Writing to
SDHCI_BLOCK_SIZE register when CQE is enabled results
On Wed, 2018-12-19 at 15:30 -0500, Steven Rostedt wrote:
> On Wed, 19 Dec 2018 12:20:19 -0800
> Joe Perches wrote:
>
> > > Yeah, I had considered it but wasn't sure it was worth it. Since
> > > you're suggesting it is, I can send another patch on top of
> > > these, or
> > > feel free if you
On Thu, 6 Dec 2018 09:09:12 +0800, Jianjun Wang wrote:
> MT7629 is an arm platform Soc which has the same PCIe IP with MT7622.
>
> Signed-off-by: Jianjun Wang
> ---
> Documentation/devicetree/bindings/pci/mediatek-pcie.txt | 1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: Rob Herring
Pavel
On 12/19/2018 02:10 PM, Pavel Machek wrote:
> On Wed 2018-12-19 13:41:18, Dan Murphy wrote:
>> Pavel
>>
>> Thanks for the review.
>>
>> On 12/19/2018 01:34 PM, Pavel Machek wrote:
>>> Hi!
>>>
+static DEVICE_ATTR_WO(ctrl_bank_a_mix);
+static DEVICE_ATTR_WO(ctrl_bank_b_mix);
> On Dec 18, 2018, at 11:53 AM, Vineet Gupta wrote:
>
> Use on-stack smaller buffers instead of dynamic pages.
>
> The motivation for this change was to address lockdep splat when
> signal handling code calls show_regs (with preemption disabled) and
> ARC show_regs calls into sleepable page
On Tue 18-12-18 15:46:45, prakash.sangappa wrote:
[...]
> Dave Hansen asked how would it scale, with respect reading this file from
> a large process. Answer is, the file contents are generated using page
> table walk, and copied to user buffer. The mmap_sem lock is drop and
> re-acquired in the
On Wed, 2018-12-19 at 15:34 -0500, Steven Rostedt wrote:
> On Wed, 19 Dec 2018 12:22:38 -0800
> Joe Perches wrote:
>
> > On Wed, 2018-12-19 at 14:16 -0600, Tom Zanussi wrote:
> > > How's this?
> > >
> > > [PATCH] tracing: Introduce and use strcmp_const() for hist triggers
> > >
> > > Provide a
On 12/19/18 12:32 PM, Paolo Bonzini wrote:
> On 19/12/18 05:12, Stephen Rothwell wrote:
>> I fixed it up (the former removed some code updated by the latter, so I
>> did that) and can carry the fix as necessary. This is now fixed as far as
>> linux-next is concerned, but any non trivial conflicts
On Wed, Dec 19, 2018 at 12:32 PM Michal Hocko wrote:
>
> On Mon 17-12-18 20:23:23, Dan Williams wrote:
> > Andrew, this needs at least an ack from Michal, or Mel before it moves
> > forward. It would be a nice surprise / present to see it move forward
> > before the holidays, but I suspect it may
Hi Niklas,
On Wed, Dec 12, 2018 at 11:07:17PM +0100, Niklas Cassel wrote:
> On Tue, Dec 04, 2018 at 02:42:29PM -0800, Matthias Kaehlcke wrote:
> > Get the ref clock of the PHY from the device tree instead of
> > hardcoding its name and rate.
> >
> > Signed-off-by: Matthias Kaehlcke
> > ---
> >
On 19/12/18 21:54, Dave Hansen wrote:
> I should have called this out in the changelog, but I removed *all* the
> support because I assumed that guests don't need MPX because no other OS
> supported it that I know of.
Well, as long as you could have code that sets the MPX bits in XCR0, KVM
will
On Wed, 19 Dec 2018 14:38:39 -0600
Tom Zanussi wrote:
> On Wed, 2018-12-19 at 15:30 -0500, Steven Rostedt wrote:
> > On Wed, 19 Dec 2018 12:20:19 -0800
> > Joe Perches wrote:
> >
> > > > Yeah, I had considered it but wasn't sure it was worth it. Since
> > > > you're suggesting it is, I can
On Wed, 19 Dec 2018 12:51:59 -0800
Joe Perches wrote:
> > #define strncmp_prefix(str, prefix) \
> > strncmp(str, prefix, strlen(prefix))
> >
> > in include/linux/string.h
> >
> > And go around and use that throughout the kernel. By doing a quick
> > grep, I already spotted a few bugs.
>
Hi Song,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on bpf-next/master]
url:
https://github.com/0day-ci/linux/commits/Song-Liu/perf-bpf-Introduce-PERF_RECORD_KSYMBOL/20181220-023635
base: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git
When viewing the /proc//status file, one can see output lines like
Cpus_allowed: ,,
Cpus_allowed_list:0-95
Mems_allowed:
On Wed, 2018-12-19 at 16:01 -0500, Steven Rostedt wrote:
> On Wed, 19 Dec 2018 14:38:39 -0600
> Tom Zanussi wrote:
>
> > On Wed, 2018-12-19 at 15:30 -0500, Steven Rostedt wrote:
> > > On Wed, 19 Dec 2018 12:20:19 -0800
> > > Joe Perches wrote:
> > >
> > > > > Yeah, I had considered it but
Fixed a coding style mistake by adding the SPDX identifier tag to the
first line of the code.
Signed-off-by: Amir Mahdi Ghorbanian
---
drivers/staging/iio/accel/adis16240.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/iio/accel/adis16240.c
On Wed, 19 Dec 2018, Paul Burton wrote:
> On Sat, Dec 15, 2018 at 11:19:37AM -0800, Andy Lutomirski wrote:
> > The really simple but possibly suboptimal fix is to get rid of
> > VM_WRITE and to use get_user_pages(..., FOLL_FORCE) to write to it.
>
> I actually wound up trying this route because
On 19/12/18 17:25, Vitaly Kuznetsov wrote:
> Recent optimizations in MMU code broke nested SVM with NPT in L1
> completely: when we do nested_svm_{,un}init_mmu_context() we want
> to switch from TDP MMU to shadow MMU, both init_kvm_tdp_mmu() and
> kvm_init_shadow_mmu() check if re-configuration is
This patch adjust the print string of drm_display_mode object
to remove drm_mode_object dependency in omapdrm files.
Signed-off-by: Shayenne Moura
---
drivers/gpu/drm/omapdrm/omap_connector.c | 9 ++---
drivers/gpu/drm/omapdrm/omap_crtc.c | 8 ++--
2 files changed, 4 insertions(+),
This patch adjust the print string of drm_display_mode object
to remove drm_mode_object dependency in msm files.
Signed-off-by: Shayenne Moura
---
drivers/gpu/drm/msm/disp/mdp4/mdp4_crtc.c | 10 ++
drivers/gpu/drm/msm/disp/mdp4/mdp4_dsi_encoder.c | 9 +
This patch serie removes drm_mode_object dependency from
drm_display_mode struct. This is part of KMS cleanup.
The motivation is that a display mode is a normal modeset object,
possibly including public userspace id.
This can be removed since the entire concept of userspace
managing modes
This patch adjust the print string of drm_display_mode object
to remove drm_mode_object dependency in sti files.
Signed-off-by: Shayenne Moura
---
drivers/gpu/drm/sti/sti_crtc.c | 16
1 file changed, 4 insertions(+), 12 deletions(-)
diff --git a/drivers/gpu/drm/sti/sti_crtc.c
This patch adjust the print string of drm_display_mode object
to remove drm_mode_object dependency in meson files.
Signed-off-by: Shayenne Moura
---
drivers/gpu/drm/meson/meson_dw_hdmi.c | 12 +++-
1 file changed, 3 insertions(+), 9 deletions(-)
diff --git
On 03/12/18 10:30, KarimAllah Ahmed wrote:
> +void kvm_vcpu_unmap(struct kvm_host_map *map)
This probably needs to come in two versions, dirty and clean. I'll do
the adjustment when I queue this for 4.22.
Thanks,
Paolo
> +{
> + if (!map->hva)
> + return;
> +
> + if
Hi Miklos,
I love your patch! Yet something to improve:
[auto build test ERROR on fuse/for-next]
[cannot apply to v4.20-rc7 next-20181219]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Vivek
On 06/12/18 17:01, Konrad Rzeszutek Wilk wrote:
> On Mon, Dec 03, 2018 at 10:30:53AM +0100, KarimAllah Ahmed wrote:
>> Guest memory can either be directly managed by the kernel (i.e. have a
>> "struct
>> page") or they can simply live outside kernel control (i.e. do not have a
>> "struct page").
This patch removes the drm_mode_object prints, evaluation and use from
drm_display_mode objects used in drm files. It removes dependency from
drm_mode_object.
Signed-off-by: Shayenne Moura
---
drivers/gpu/drm/drm_crtc_helper.c | 5 ++---
drivers/gpu/drm/drm_modes.c | 5 -
2 files
This patch adjust the print string of drm_display_mode object
to remove drm_mode_object dependency in i915 files. It modifies
the print style to standardize the use of DRM_MODE_FMT.
Signed-off-by: Shayenne Moura
---
drivers/gpu/drm/i915/i915_debugfs.c | 9 +
1 file changed, 1
On 12/19/18 1:00 PM, Paolo Bonzini wrote:
> On 19/12/18 21:54, Dave Hansen wrote:
>> I should have called this out in the changelog, but I removed *all* the
>> support because I assumed that guests don't need MPX because no other OS
>> supported it that I know of.
>
> Well, as long as you could
This patch finalizes the KMS cleanup task dependency from
drm_display_mode. It removes the use of drm_mode_object
from drm_display_mode struct and it removes the use of
base.id and base.type from drm_display_mode struct
print string.
Signed-off-by: Shayenne Moura
---
include/drm/drm_modes.h |
Since 4.19.5 I have not been able to boot kernels on my Xen-hosted VM on
a system with an Intel Xeon L5520 processor (microcode 0x1d).
4.19.4 worked fine; I've tried kernels 4.19.5, 4.19.6, 4.19.7 4.19.9, 4.19.10,
4.20-rc7, and they all throw:
BUG: unable to handle kernel paging request at
Create x86_64 specific version of memset for user space, based on
clear_user().
This will be used for implementing wr_memset() in the __wr_after_init
scenario, where write-rare variables have an alternate mapping for
writing.
Signed-off-by: Igor Stoppa
CC: Andy Lutomirski
CC: Nadav Amit
CC:
Introduce a section and a label for statically allocated write rare
data. The label is named "__wr_after_init".
As the name implies, after the init phase is completed, this section
will be modifiable only by invoking write rare functions.
The section must take up a set of full pages.
To activate
Patch-set implementing write-rare memory protection for statically
allocated data.
Its purpose it to keep data write protected kernel data which is seldom
modified.
There is no read overhead, however writing requires special operations that
are probably unsitable for often-changing data.
The use
To avoid code duplication, re-use __memset_user(), when clearing
user-space memory.
The overhead should be minimal (2 extra register assignments) and
outside of the writing loop.
Signed-off-by: Igor Stoppa
CC: Andy Lutomirski
CC: Nadav Amit
CC: Matthew Wilcox
CC: Peter Zijlstra
CC: Kees
Update the self-protection documentation, to mention also the use of the
__wr_after_init attribute.
Signed-off-by: Igor Stoppa
CC: Andy Lutomirski
CC: Nadav Amit
CC: Matthew Wilcox
CC: Peter Zijlstra
CC: Kees Cook
CC: Dave Hansen
CC: Mimi Zohar
CC: linux-integr...@vger.kernel.org
CC:
Set of test cases meant to confirm that the write rare functionality
works as expected.
It can be optionally compiled as module.
Signed-off-by: Igor Stoppa
CC: Andy Lutomirski
CC: Nadav Amit
CC: Matthew Wilcox
CC: Peter Zijlstra
CC: Kees Cook
CC: Dave Hansen
CC: Mimi Zohar
CC:
The policy flags could be targeted by an attacker aiming at disabling IMA,
so that there would be no trace of a file system modification in the
measurement list.
Since the flags can be altered at runtime, it is not possible to make
them become fully read-only, for example with __ro_after_init.
The write protection of the __wr_after_init data can be verified with the
same methodology used for const data.
Signed-off-by: Igor Stoppa
CC: Andy Lutomirski
CC: Nadav Amit
CC: Matthew Wilcox
CC: Peter Zijlstra
CC: Kees Cook
CC: Dave Hansen
CC: Mimi Zohar
CC:
After each write operation, confirm that it was successful, otherwise
generate a warning.
Signed-off-by: Igor Stoppa
CC: Andy Lutomirski
CC: Nadav Amit
CC: Matthew Wilcox
CC: Peter Zijlstra
CC: Kees Cook
CC: Dave Hansen
CC: Mimi Zohar
CC: linux-integr...@vger.kernel.org
CC:
601 - 700 of 949 matches
Mail list logo
