On Tue, 7 Aug 2018, Ard Biesheuvel wrote:
> On 7 August 2018 at 19:39, Mikulas Patocka wrote:
> >
> >
> > On Tue, 7 Aug 2018, Marcin Wojtas wrote:
> >
> >> Ard, Mikulas,
> >>
> >> After some self-caused setup issues I was able to run the test on my
> >> MacchiatoBin with the kernel v4.18-rc8.
On Tue, 7 Aug 2018, Ard Biesheuvel wrote:
> On 7 August 2018 at 19:39, Mikulas Patocka wrote:
> >
> >
> > On Tue, 7 Aug 2018, Marcin Wojtas wrote:
> >
> >> Ard, Mikulas,
> >>
> >> After some self-caused setup issues I was able to run the test on my
> >> MacchiatoBin with the kernel v4.18-rc8.
On Tue, Jul 31, 2018 at 06:27:24PM +0530, Sibi S wrote:
> Hi Philipp,
> Thanks for the review!
>
> On 07/31/2018 02:12 PM, Philipp Zabel wrote:
> > Hi Sibi,
> >
> > On Fri, 2018-07-27 at 20:58 +0530, Sibi Sankar wrote:
> > > Add SDM845 PDC (Power Domain Controller) reset controller binding
> > >
On Tue, Jul 31, 2018 at 06:27:24PM +0530, Sibi S wrote:
> Hi Philipp,
> Thanks for the review!
>
> On 07/31/2018 02:12 PM, Philipp Zabel wrote:
> > Hi Sibi,
> >
> > On Fri, 2018-07-27 at 20:58 +0530, Sibi Sankar wrote:
> > > Add SDM845 PDC (Power Domain Controller) reset controller binding
> > >
GENERIC_CPU_VULNERABILITIES provide a common way to figure out if a
system is affected by vulnerabilities like meltdown and other variants
of spectre. This small series adds support for it in arm64.
Thank you,
Best regards,
Yousaf
Mian Yousaf Kaukab (6):
arm64: kpti: move check for
GENERIC_CPU_VULNERABILITIES provide a common way to figure out if a
system is affected by vulnerabilities like meltdown and other variants
of spectre. This small series adds support for it in arm64.
Thank you,
Best regards,
Yousaf
Mian Yousaf Kaukab (6):
arm64: kpti: move check for
Hard-coded since patches are merged and there are no configuration
options.
Signed-off-by: Mian Yousaf Kaukab
---
arch/arm64/kernel/cpu_errata.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm64/kernel/cpu_errata.c b/arch/arm64/kernel/cpu_errata.c
index
Hard-coded since patches are merged and there are no configuration
options.
Signed-off-by: Mian Yousaf Kaukab
---
arch/arm64/kernel/cpu_errata.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm64/kernel/cpu_errata.c b/arch/arm64/kernel/cpu_errata.c
index
Only report mitigation present if hardening callback has been
successfully installed.
Signed-off-by: Mian Yousaf Kaukab
---
arch/arm64/kernel/cpu_errata.c | 34 +-
1 file changed, 33 insertions(+), 1 deletion(-)
diff --git a/arch/arm64/kernel/cpu_errata.c
Checking CSV3 support directly in case CONFIG_UNMAP_KERNEL_AT_EL0
is not enabled.
Signed-off-by: Mian Yousaf Kaukab
---
arch/arm64/kernel/cpu_errata.c | 24
1 file changed, 24 insertions(+)
diff --git a/arch/arm64/kernel/cpu_errata.c b/arch/arm64/kernel/cpu_errata.c
Only report mitigation present if hardening callback has been
successfully installed.
Signed-off-by: Mian Yousaf Kaukab
---
arch/arm64/kernel/cpu_errata.c | 34 +-
1 file changed, 33 insertions(+), 1 deletion(-)
diff --git a/arch/arm64/kernel/cpu_errata.c
Checking CSV3 support directly in case CONFIG_UNMAP_KERNEL_AT_EL0
is not enabled.
Signed-off-by: Mian Yousaf Kaukab
---
arch/arm64/kernel/cpu_errata.c | 24
1 file changed, 24 insertions(+)
diff --git a/arch/arm64/kernel/cpu_errata.c b/arch/arm64/kernel/cpu_errata.c
Return status based no ssbd_state. Return string "Unknown" in case
CONFIG_ARM64_SSBD is disabled or arch workaround2 is not available
in the firmware.
Signed-off-by: Mian Yousaf Kaukab
---
arch/arm64/kernel/cpu_errata.c | 20
1 file changed, 20 insertions(+)
diff --git
Return status based no ssbd_state. Return string "Unknown" in case
CONFIG_ARM64_SSBD is disabled or arch workaround2 is not available
in the firmware.
Signed-off-by: Mian Yousaf Kaukab
---
arch/arm64/kernel/cpu_errata.c | 20
1 file changed, 20 insertions(+)
diff --git
Enable CPU vulnerabilty show functions for spectre_v1, spectre_v2,
meltdown and store-bypass.
Signed-off-by: Mian Yousaf Kaukab
---
arch/arm64/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index 0dec01a0c81c..ffd97bc0f5d5 100644
---
Enable CPU vulnerabilty show functions for spectre_v1, spectre_v2,
meltdown and store-bypass.
Signed-off-by: Mian Yousaf Kaukab
---
arch/arm64/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index 0dec01a0c81c..ffd97bc0f5d5 100644
---
Prepare to call it in generic cpu vulnerabilities support.
Signed-off-by: Mian Yousaf Kaukab
---
arch/arm64/include/asm/cpufeature.h | 16
arch/arm64/kernel/cpufeature.c | 9 +
2 files changed, 17 insertions(+), 8 deletions(-)
diff --git
Prepare to call it in generic cpu vulnerabilities support.
Signed-off-by: Mian Yousaf Kaukab
---
arch/arm64/include/asm/cpufeature.h | 16
arch/arm64/kernel/cpufeature.c | 9 +
2 files changed, 17 insertions(+), 8 deletions(-)
diff --git
On Fri, Aug 3, 2018 at 3:34 PM Helge Deller wrote:
>
> On 03.08.2018 22:33, Nick Desaulniers wrote:
> > On Fri, Aug 3, 2018 at 12:09 PM John David Anglin
> > wrote:
> >>
> >> On 2018-08-03 2:11 PM, Nick Desaulniers wrote:
> >>> But the kernel uses the generic_THIS_IP_ *everywhere*, not
On Fri, Aug 3, 2018 at 3:34 PM Helge Deller wrote:
>
> On 03.08.2018 22:33, Nick Desaulniers wrote:
> > On Fri, Aug 3, 2018 at 12:09 PM John David Anglin
> > wrote:
> >>
> >> On 2018-08-03 2:11 PM, Nick Desaulniers wrote:
> >>> But the kernel uses the generic_THIS_IP_ *everywhere*, not
On Fri, Jul 27, 2018 at 02:15:15PM +0200, Michal Vokáč wrote:
> Y Soft is headquartered in the Czech Republic and it is a worldwide
> provider of enterprise office solutions for print management.
>
> Signed-off-by: Michal Vokáč
> ---
> I work towards upstreaming support for our custom i.MX6
On Fri, Jul 27, 2018 at 02:15:15PM +0200, Michal Vokáč wrote:
> Y Soft is headquartered in the Czech Republic and it is a worldwide
> provider of enterprise office solutions for print management.
>
> Signed-off-by: Michal Vokáč
> ---
> I work towards upstreaming support for our custom i.MX6
On 7 August 2018 at 19:39, Mikulas Patocka wrote:
>
>
> On Tue, 7 Aug 2018, Marcin Wojtas wrote:
>
>> Ard, Mikulas,
>>
>> After some self-caused setup issues I was able to run the test on my
>> MacchiatoBin with the kernel v4.18-rc8. It's been running for 1h+ now,
>> loading the CPU to 100% and
On 7 August 2018 at 19:39, Mikulas Patocka wrote:
>
>
> On Tue, 7 Aug 2018, Marcin Wojtas wrote:
>
>> Ard, Mikulas,
>>
>> After some self-caused setup issues I was able to run the test on my
>> MacchiatoBin with the kernel v4.18-rc8. It's been running for 1h+ now,
>> loading the CPU to 100% and
On 8/7/18 7:59 AM, Vlastimil Babka wrote:
On 07/26/2018 08:10 PM, Yang Shi wrote:
Introduces three new helper functions:
* munmap_addr_sanity()
* munmap_lookup_vma()
* munmap_mlock_vma()
They will be used by do_munmap() and the new do_munmap with zapping
large mapping early in the
On 8/7/18 7:59 AM, Vlastimil Babka wrote:
On 07/26/2018 08:10 PM, Yang Shi wrote:
Introduces three new helper functions:
* munmap_addr_sanity()
* munmap_lookup_vma()
* munmap_mlock_vma()
They will be used by do_munmap() and the new do_munmap with zapping
large mapping early in the
On Fri, Jul 20, 2018 at 10:54 AM, Doug Anderson wrote:
> [...]
Apologies for this noise. I have nothing to add to this specific
conversation. :)
Doug and I (via our @chromium.org accounts) have had DKIM issues. This
is a test to see if it really has been solved. (The "sender" field was
being
On Fri, Jul 20, 2018 at 10:54 AM, Doug Anderson wrote:
> [...]
Apologies for this noise. I have nothing to add to this specific
conversation. :)
Doug and I (via our @chromium.org accounts) have had DKIM issues. This
is a test to see if it really has been solved. (The "sender" field was
being
On Tue, Jul 17, 2018 at 06:05:09PM +0200, Paweł Chmiel wrote:
> This patch adds devicetree bindings documentation for
> battery charging controller as the subnode of MAX8998 PMIC.
>
> Signed-off-by: Paweł Chmiel
> ---
> Changes from v2:
> - Make charge-restart-level-microvolt optional.
> -
On Tue, Jul 17, 2018 at 06:05:09PM +0200, Paweł Chmiel wrote:
> This patch adds devicetree bindings documentation for
> battery charging controller as the subnode of MAX8998 PMIC.
>
> Signed-off-by: Paweł Chmiel
> ---
> Changes from v2:
> - Make charge-restart-level-microvolt optional.
> -
On 08/06/2018 05:35 PM, James Bottomley wrote:
> On Mon, 2018-08-06 at 17:09 -0700, Tadeusz Struk wrote:
>> On 08/06/2018 04:05 PM, James Bottomley wrote:
>>> For an async interface, shouldn't I be able to queue an
>>> arbitrary number of commands without blocking?
>>
>> That was the approach in
On 08/06/2018 05:35 PM, James Bottomley wrote:
> On Mon, 2018-08-06 at 17:09 -0700, Tadeusz Struk wrote:
>> On 08/06/2018 04:05 PM, James Bottomley wrote:
>>> For an async interface, shouldn't I be able to queue an
>>> arbitrary number of commands without blocking?
>>
>> That was the approach in
From: Sean Wang
This adds a driver based on serdev driver for the MediaTek serial protocol
based on running H:4, which can enable the built-in Bluetooth device inside
MT7622 SoC.
Signed-off-by: Sean Wang
Signed-off-by: Marcel Holtmann
---
drivers/bluetooth/Kconfig | 11 +
From: Sean Wang
This adds a driver based on serdev driver for the MediaTek serial protocol
based on running H:4, which can enable the built-in Bluetooth device inside
MT7622 SoC.
Signed-off-by: Sean Wang
Signed-off-by: Marcel Holtmann
---
drivers/bluetooth/Kconfig | 11 +
From: Sean Wang
v10 and changes since v9:
- Add a fixup that is __be16 is required instead of dlen1 + dlen2 in STP
header.
- Align a few one-line comments style as they're made in v9
- Fix two warnings catched by checkpatch.pl
WARNING:TYPO_SPELLING: 'specifc' may be misspelled -
From: Sean Wang
Add binding document for a SoC built-in device using MediaTek protocol.
Which could be found on MT7622 SoC or other similar MediaTek SoCs.
Signed-off-by: Sean Wang
Reviewed-by: Rob Herring
Signed-off-by: Marcel Holtmann
---
.../devicetree/bindings/net/mediatek-bluetooth.txt
From: Sean Wang
Add an entry for the MediaTek Bluetooth driver.
Signed-off-by: Sean Wang
Signed-off-by: Marcel Holtmann
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 0f2cce4..e983d9e 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@
From: Sean Wang
v10 and changes since v9:
- Add a fixup that is __be16 is required instead of dlen1 + dlen2 in STP
header.
- Align a few one-line comments style as they're made in v9
- Fix two warnings catched by checkpatch.pl
WARNING:TYPO_SPELLING: 'specifc' may be misspelled -
From: Sean Wang
Add binding document for a SoC built-in device using MediaTek protocol.
Which could be found on MT7622 SoC or other similar MediaTek SoCs.
Signed-off-by: Sean Wang
Reviewed-by: Rob Herring
Signed-off-by: Marcel Holtmann
---
.../devicetree/bindings/net/mediatek-bluetooth.txt
From: Sean Wang
Add an entry for the MediaTek Bluetooth driver.
Signed-off-by: Sean Wang
Signed-off-by: Marcel Holtmann
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 0f2cce4..e983d9e 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@
On Wed, Aug 01, 2018 at 12:49:39PM +0200, John Crispin wrote:
> This patch adds the binding documentation for the HS/SS USB PHY found
> inside Qualcomm Dakota SoCs.
>
> Cc: Rob Herring
> Cc: devicet...@vger.kernel.org
> Signed-off-by: John Crispin
> ---
>
On Wed, Aug 01, 2018 at 12:49:39PM +0200, John Crispin wrote:
> This patch adds the binding documentation for the HS/SS USB PHY found
> inside Qualcomm Dakota SoCs.
>
> Cc: Rob Herring
> Cc: devicet...@vger.kernel.org
> Signed-off-by: John Crispin
> ---
>
On Tue, Aug 07, 2018 at 01:50:09PM +0200, peter enderborg wrote:
> On 08/01/2018 05:19 PM, Johannes Weiner wrote:
> >
> > A kernel with CONFIG_PSI=y will create a /proc/pressure directory with
> > 3 files: cpu, memory, and io. If using cgroup2, cgroups will also have
> > cpu.pressure,
On Tue, Aug 07, 2018 at 10:35:42AM -0700, Dave Hansen wrote:
> On 08/07/2018 10:17 AM, kan.li...@linux.intel.com wrote:
> > Denverton and Gemini Lake are platform names and should not be used for
> > Processor Family stuff. The microarchitecture codename should be used.
>
> Why?
>
> Denverton is
On Tue, Aug 07, 2018 at 01:50:09PM +0200, peter enderborg wrote:
> On 08/01/2018 05:19 PM, Johannes Weiner wrote:
> >
> > A kernel with CONFIG_PSI=y will create a /proc/pressure directory with
> > 3 files: cpu, memory, and io. If using cgroup2, cgroups will also have
> > cpu.pressure,
On Tue, Aug 07, 2018 at 10:35:42AM -0700, Dave Hansen wrote:
> On 08/07/2018 10:17 AM, kan.li...@linux.intel.com wrote:
> > Denverton and Gemini Lake are platform names and should not be used for
> > Processor Family stuff. The microarchitecture codename should be used.
>
> Why?
>
> Denverton is
On Wed, Aug 01, 2018 at 09:09:06AM +0530, Manivannan Sadhasivam wrote:
> Since the clock and reset management units are sharing the same memory
> map, document the clock bindings to support System Controller.
This is no reason to add child nodes. The existing node can be both a
clock and reset
On Wed, Aug 01, 2018 at 09:09:06AM +0530, Manivannan Sadhasivam wrote:
> Since the clock and reset management units are sharing the same memory
> map, document the clock bindings to support System Controller.
This is no reason to add child nodes. The existing node can be both a
clock and reset
On Mon, Aug 06, 2018 at 08:54:10PM +0200, Alexandre Belloni wrote:
> The Microsemi Ocelot I2C controller is a designware IP. It also has a
> second set of registers to allow tweaking SDA hold time and spike
> filtering.
>
> Cc: Rob Herring
> Reviewed-by: Andy Shevchenko
> Signed-off-by:
On Mon, Aug 06, 2018 at 08:54:10PM +0200, Alexandre Belloni wrote:
> The Microsemi Ocelot I2C controller is a designware IP. It also has a
> second set of registers to allow tweaking SDA hold time and spike
> filtering.
>
> Cc: Rob Herring
> Reviewed-by: Andy Shevchenko
> Signed-off-by:
This issue was discovered on a 4.9-based android device, but the
relevant mainline code appears to be the same. The symptom is that
over time the some workloads become sluggish resulting in missed
frames or sluggishness. It appears to be the same issue described in
This issue was discovered on a 4.9-based android device, but the
relevant mainline code appears to be the same. The symptom is that
over time the some workloads become sluggish resulting in missed
frames or sluggishness. It appears to be the same issue described in
On Tue, 7 Aug 2018, Marcin Wojtas wrote:
> Ard, Mikulas,
>
> After some self-caused setup issues I was able to run the test on my
> MacchiatoBin with the kernel v4.18-rc8. It's been running for 1h+ now,
> loading the CPU to 100% and no single error event...
>
> I built the binary file with:
On Tue, 7 Aug 2018, Marcin Wojtas wrote:
> Ard, Mikulas,
>
> After some self-caused setup issues I was able to run the test on my
> MacchiatoBin with the kernel v4.18-rc8. It's been running for 1h+ now,
> loading the CPU to 100% and no single error event...
>
> I built the binary file with:
On 08/07/2018 10:17 AM, kan.li...@linux.intel.com wrote:
> Denverton and Gemini Lake are platform names and should not be used for
> Processor Family stuff. The microarchitecture codename should be used.
Why?
Denverton is the platform. "Goldmont" is literally the
microarchitecture, and you are
On 08/07/2018 10:17 AM, kan.li...@linux.intel.com wrote:
> Denverton and Gemini Lake are platform names and should not be used for
> Processor Family stuff. The microarchitecture codename should be used.
Why?
Denverton is the platform. "Goldmont" is literally the
microarchitecture, and you are
On 07.08.2018 19:15, Pierre Morel wrote:
> On 07/08/2018 14:51, David Hildenbrand wrote:
>> While discussing AP changes, we discovered that we will have to force
>> a CPU using the vSIE to regenerate/reload shadow data structures. For now,
>> we have no mechanism for that.
>>
>> E.g. when clearing
On 07.08.2018 19:15, Pierre Morel wrote:
> On 07/08/2018 14:51, David Hildenbrand wrote:
>> While discussing AP changes, we discovered that we will have to force
>> a CPU using the vSIE to regenerate/reload shadow data structures. For now,
>> we have no mechanism for that.
>>
>> E.g. when clearing
On Tue, Aug 07, 2018 at 10:17:27AM -0700, kan.li...@linux.intel.com wrote:
> From: Kan Liang
>
> Denverton and Gemini Lake are platform names and should not be used for
> Processor Family stuff. The microarchitecture codename should be used.
>
> DENVERTON is Goldmont server SoC. Rename
On Tue, Aug 07, 2018 at 10:17:27AM -0700, kan.li...@linux.intel.com wrote:
> From: Kan Liang
>
> Denverton and Gemini Lake are platform names and should not be used for
> Processor Family stuff. The microarchitecture codename should be used.
>
> DENVERTON is Goldmont server SoC. Rename
On Tue, Aug 07, 2018 at 11:29:54AM -0400, Liang, Kan wrote:
> On 8/6/2018 2:35 PM, Peter Zijlstra wrote:
> > On Mon, Aug 06, 2018 at 10:23:42AM -0700, kan.li...@linux.intel.com wrote:
> > > @@ -2044,6 +2056,14 @@ static void intel_pmu_disable_event(struct
> > > perf_event *event)
> > >
On Tue, Aug 07, 2018 at 11:29:54AM -0400, Liang, Kan wrote:
> On 8/6/2018 2:35 PM, Peter Zijlstra wrote:
> > On Mon, Aug 06, 2018 at 10:23:42AM -0700, kan.li...@linux.intel.com wrote:
> > > @@ -2044,6 +2056,14 @@ static void intel_pmu_disable_event(struct
> > > perf_event *event)
> > >
Kernel addresses are always mapped with _PAGE_USER=0, i.e. PKRU
isn't enforced, and so we should never see X86_PF_PK set on a
kernel address fault. WARN once to capture the issue in case we
somehow don't die, e.g. the access originated in userspace.
Remove a similar check and its comment from
Kernel addresses are always mapped with _PAGE_USER=0, i.e. PKRU
isn't enforced, and so we should never see X86_PF_PK set on a
kernel address fault. WARN once to capture the issue in case we
somehow don't die, e.g. the access originated in userspace.
Remove a similar check and its comment from
On Tue, Aug 7, 2018 at 10:19 AM Matthias Kaehlcke wrote:
>
> The driver expects to find the device id in rt5677_of_match.data, however
> it is currently assigned to rt5677_of_match.type. Fix this.
>
> The problem was found with the help of clang:
> sound/soc/codecs/rt5677.c:5010:36: warning:
On Tue, Aug 7, 2018 at 10:19 AM Matthias Kaehlcke wrote:
>
> The driver expects to find the device id in rt5677_of_match.data, however
> it is currently assigned to rt5677_of_match.type. Fix this.
>
> The problem was found with the help of clang:
> sound/soc/codecs/rt5677.c:5010:36: warning:
On Thu, Aug 02, 2018 at 08:18:59PM -0400, Brian Masney wrote:
> This patch adds avago,apds9930 to the tsl2772 bindings.
>
> Signed-off-by: Brian Masney
> ---
> Documentation/devicetree/bindings/iio/light/tsl2772.txt | 1 +
> 1 file changed, 1 insertion(+)
Reviewed-by: Rob Herring
On Thu, Aug 02, 2018 at 08:18:59PM -0400, Brian Masney wrote:
> This patch adds avago,apds9930 to the tsl2772 bindings.
>
> Signed-off-by: Brian Masney
> ---
> Documentation/devicetree/bindings/iio/light/tsl2772.txt | 1 +
> 1 file changed, 1 insertion(+)
Reviewed-by: Rob Herring
On Fri, Aug 03, 2018 at 10:51:23PM +0100, Jonathan Cameron wrote:
> On Thu, 2 Aug 2018 20:18:57 -0400
> Brian Masney wrote:
>
> > This patch adds device tree bindings to the tsl2772 driver for the
> > regulator framework.
> >
> > Signed-off-by: Brian Masney
> I suspect Rob will tell you this
On Fri, Aug 03, 2018 at 10:51:23PM +0100, Jonathan Cameron wrote:
> On Thu, 2 Aug 2018 20:18:57 -0400
> Brian Masney wrote:
>
> > This patch adds device tree bindings to the tsl2772 driver for the
> > regulator framework.
> >
> > Signed-off-by: Brian Masney
> I suspect Rob will tell you this
The driver expects to find the device id in rt5677_of_match.data, however
it is currently assigned to rt5677_of_match.type. Fix this.
The problem was found with the help of clang:
sound/soc/codecs/rt5677.c:5010:36: warning: expression which evaluates to
zero treated as a null pointer constant
The driver expects to find the device id in rt5677_of_match.data, however
it is currently assigned to rt5677_of_match.type. Fix this.
The problem was found with the help of clang:
sound/soc/codecs/rt5677.c:5010:36: warning: expression which evaluates to
zero treated as a null pointer constant
From: Kan Liang
Denverton and Gemini Lake are platform names and should not be used for
Processor Family stuff. The microarchitecture codename should be used.
DENVERTON is Goldmont server SoC. Rename DENVERTON to GOLDMONT2, similar
to SILVERMONT2 being the silvermont server SoCs.
Rename
From: Kan Liang
Denverton and Gemini Lake are platform names and should not be used for
Processor Family stuff. The microarchitecture codename should be used.
DENVERTON is Goldmont server SoC. Rename DENVERTON to GOLDMONT2, similar
to SILVERMONT2 being the silvermont server SoCs.
Rename
On 07/08/2018 14:51, David Hildenbrand wrote:
While discussing AP changes, we discovered that we will have to force
a CPU using the vSIE to regenerate/reload shadow data structures. For now,
we have no mechanism for that.
E.g. when clearing AP masks later, we could still have a vSIE CPU making
On 07/08/2018 14:51, David Hildenbrand wrote:
While discussing AP changes, we discovered that we will have to force
a CPU using the vSIE to regenerate/reload shadow data structures. For now,
we have no mechanism for that.
E.g. when clearing AP masks later, we could still have a vSIE CPU making
On Mon, 9 Jul 2018 17:53:09 -0500
"Gustavo A. R. Silva" wrote:
> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
> where we are expecting to fall through.
>
> Signed-off-by: Gustavo A. R. Silva
> ---
> drivers/vfio/pci/vfio_pci.c | 2 +-
>
On Mon, 9 Jul 2018 17:53:09 -0500
"Gustavo A. R. Silva" wrote:
> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
> where we are expecting to fall through.
>
> Signed-off-by: Gustavo A. R. Silva
> ---
> drivers/vfio/pci/vfio_pci.c | 2 +-
>
On Tue, 2018-08-07 at 18:43 +0800, Baolin Wang wrote:
>
> +static u32 sprd_spi_transfer_max_timeout(struct sprd_spi *ss,
> + struct spi_transfer *t)
> +{
> + /*
> + * The time spent on transmission of the full FIFO data is the maximum
> + * SPI
On Tue, 2018-08-07 at 18:43 +0800, Baolin Wang wrote:
>
> +static u32 sprd_spi_transfer_max_timeout(struct sprd_spi *ss,
> + struct spi_transfer *t)
> +{
> + /*
> + * The time spent on transmission of the full FIFO data is the maximum
> + * SPI
On 07/08/2018 14:51, David Hildenbrand wrote:
When we change the crycb (or execution controls), we also have to make sure
that the vSIE shadow datastructures properly consider the changed
values before rerunning the vSIE. We can achieve that by simply using a
VCPU request now.
This has to be a
On 07/08/2018 14:51, David Hildenbrand wrote:
When we change the crycb (or execution controls), we also have to make sure
that the vSIE shadow datastructures properly consider the changed
values before rerunning the vSIE. We can achieve that by simply using a
VCPU request now.
This has to be a
On 07/08/2018 14:51, David Hildenbrand wrote:
VCPU requests and VCPU blocking right now don't take care of the vSIE
(as it was not necessary until now). But we want to have VCPU requests
that will also be handled before running the vSIE again.
So let's simulate a SIE entry when entering the
On 07/08/2018 14:51, David Hildenbrand wrote:
VCPU requests and VCPU blocking right now don't take care of the vSIE
(as it was not necessary until now). But we want to have VCPU requests
that will also be handled before running the vSIE again.
So let's simulate a SIE entry when entering the
On Fri, Aug 03, 2018 at 07:58:44PM +0530, Sai Prakash Ranjan wrote:
> Introduce dynamic debug filtering mechanism to register
> tracing as dynamic_rtb() which will reduce a lot of
> overhead otherwise of tracing all the register reads/writes
> in all files.
>
> Now we can just specify the file
On Fri, Aug 03, 2018 at 07:58:44PM +0530, Sai Prakash Ranjan wrote:
> Introduce dynamic debug filtering mechanism to register
> tracing as dynamic_rtb() which will reduce a lot of
> overhead otherwise of tracing all the register reads/writes
> in all files.
>
> Now we can just specify the file
On Tue, 7 Aug 2018, Nick Desaulniers wrote:
> On Tue, Aug 7, 2018 at 12:29 AM Thomas Gleixner wrote:
> > On Mon, 6 Aug 2018, Nick Desaulniers wrote:
> > > also, there were tested by's reported:
> > >
> > > Tested-by: David Laight
> > > Tested-by: Sedat Dilek
> >
> > Which came in after I
On Tue, 7 Aug 2018, Nick Desaulniers wrote:
> On Tue, Aug 7, 2018 at 12:29 AM Thomas Gleixner wrote:
> > On Mon, 6 Aug 2018, Nick Desaulniers wrote:
> > > also, there were tested by's reported:
> > >
> > > Tested-by: David Laight
> > > Tested-by: Sedat Dilek
> >
> > Which came in after I
Commit-ID: 88c6f8a3977cc35997b47e2f99f080a15559c1eb
Gitweb: https://git.kernel.org/tip/88c6f8a3977cc35997b47e2f99f080a15559c1eb
Author: Joerg Roedel
AuthorDate: Tue, 7 Aug 2018 12:24:29 +0200
Committer: Thomas Gleixner
CommitDate: Tue, 7 Aug 2018 18:51:22 +0200
x86/mm/pti: Fix 32 bit
Commit-ID: 88c6f8a3977cc35997b47e2f99f080a15559c1eb
Gitweb: https://git.kernel.org/tip/88c6f8a3977cc35997b47e2f99f080a15559c1eb
Author: Joerg Roedel
AuthorDate: Tue, 7 Aug 2018 12:24:29 +0200
Committer: Thomas Gleixner
CommitDate: Tue, 7 Aug 2018 18:51:22 +0200
x86/mm/pti: Fix 32 bit
On Fri, Aug 03, 2018 at 10:48:38PM +0100, Jonathan Cameron wrote:
> On Thu, 2 Aug 2018 20:18:55 -0400
> Brian Masney wrote:
>
> > This patch adds the new properties amstaos,proximity-diodes and
> > led-max-microamp to the tsl2772 driver. This patch also removes the
> > driver from the
On Tue, Aug 07, 2018 at 09:39:38AM -0700, Guenter Roeck wrote:
> On Tue, Aug 7, 2018 at 9:22 AM Matthias Kaehlcke wrote:
> >
> > The initializer of rt5677_of_match contains a bogus device id
> > (enum type) for the 'type' field (char []). Remove it.
> >
> > Signed-off-by: Matthias Kaehlcke
> >
On Fri, Aug 03, 2018 at 10:48:38PM +0100, Jonathan Cameron wrote:
> On Thu, 2 Aug 2018 20:18:55 -0400
> Brian Masney wrote:
>
> > This patch adds the new properties amstaos,proximity-diodes and
> > led-max-microamp to the tsl2772 driver. This patch also removes the
> > driver from the
On Tue, Aug 07, 2018 at 09:39:38AM -0700, Guenter Roeck wrote:
> On Tue, Aug 7, 2018 at 9:22 AM Matthias Kaehlcke wrote:
> >
> > The initializer of rt5677_of_match contains a bogus device id
> > (enum type) for the 'type' field (char []). Remove it.
> >
> > Signed-off-by: Matthias Kaehlcke
> >
On Thu, Aug 02, 2018 at 09:15:53PM +0200, Marcus Folkesson wrote:
> MCP3911 is a dual channel Analog Front End (AFE) containing two
> synchronous sampling delta-sigma Analog-to-Digital Converters (ADC).
>
> Signed-off-by: Marcus Folkesson
> Signed-off-by: Kent Gustavsson
> ---
>
> Notes:
>
On Thu, Aug 02, 2018 at 09:15:53PM +0200, Marcus Folkesson wrote:
> MCP3911 is a dual channel Analog Front End (AFE) containing two
> synchronous sampling delta-sigma Analog-to-Digital Converters (ADC).
>
> Signed-off-by: Marcus Folkesson
> Signed-off-by: Kent Gustavsson
> ---
>
> Notes:
>
On Wed, Aug 01, 2018 at 05:57:42PM -0700, Saravana Kannan wrote:
> This driver registers itself as a devfreq device that allows devfreq
> governors to make bandwidth votes for an interconnect path. This allows
> applying various policies for different interconnect paths using devfreq
> governors.
On Wed, Aug 01, 2018 at 05:57:42PM -0700, Saravana Kannan wrote:
> This driver registers itself as a devfreq device that allows devfreq
> governors to make bandwidth votes for an interconnect path. This allows
> applying various policies for different interconnect paths using devfreq
> governors.
On Tue, Aug 7, 2018 at 12:29 AM Thomas Gleixner wrote:
>
> On Mon, 6 Aug 2018, Nick Desaulniers wrote:
> > On Sun, Aug 5, 2018 at 1:33 PM tip-bot for Nick Desaulniers
> > wrote:
> > > Cc: sta...@vger.kernel.org
> >
> > Not sure if this was going to be cleaned up in an automated way, but
> >
On Tue, Aug 7, 2018 at 12:29 AM Thomas Gleixner wrote:
>
> On Mon, 6 Aug 2018, Nick Desaulniers wrote:
> > On Sun, Aug 5, 2018 at 1:33 PM tip-bot for Nick Desaulniers
> > wrote:
> > > Cc: sta...@vger.kernel.org
> >
> > Not sure if this was going to be cleaned up in an automated way, but
> >
701 - 800 of 1438 matches
Mail list logo
