On Tue, Sep 10, 2019 at 08:37:19AM +, Yonghong Song wrote:
> You did not mention BPF_BINARY_HEADER_MAGIC and added member
> of `magic` in bpf_binary_header. Could you add some details
> on what is the purpose for this `magic` member?
Sure, I'll add a description to the next version.
The
On Tue, 2019-09-10 at 07:18 -0400, Steven Rostedt wrote:
> On Tue, 10 Sep 2019 11:46:56 +0300
> Sakari Ailus wrote:
>
> > There are no in-kernel %p[fF] users left. Convert the traceevent tool,
> > too, to align with the kernel.
[]
> > diff --git a/tools/lib/traceevent/event-parse.c
> >
On 05/09/19 23:22, Sean Christopherson wrote:
> Refactor x86's MSR accessors to reduce the amount of boilerplate code
> required to get/set an MSR, and consolidate the RDMSR/WRMSR emulation
> for VMX and SVM since the code is functionally identical.
>
> Sean Christopherson (2):
> KVM: x86:
> Here i2c-0 is the "local" bus, i2c-4 and i2c-5 are the remote busses on
> ports 0 and 1. As you can see the eeproms are accessed using a name like
> "4-0050", meaning physical slave address 0x50 on bus 4. No alias is needed.
>
> Should you want to know the alias, perhaps for debugging (it's
On 04/09/19 11:48, Rafael J. Wysocki wrote:
> On 8/29/2019 10:49 AM, Wanpeng Li wrote:
>> From: Wanpeng Li
>>
>> The downside of guest side polling is that polling is performed even
>> with other runnable tasks in the host. However, even if poll in kvm
>> can aware whether or not other runnable
On Tue, Sep 10, 2019 at 08:47:04PM +0530, Sheetal Tigadoli wrote:
> From: Vikas Gupta
>
> This driver registers on TEE bus to interact with OP-TEE based
> BNXT firmware management modules
>
> Signed-off-by: Vikas Gupta
> Signed-off-by: Sheetal Tigadoli
> ---
>
Add binding to define power domains as thermal warming
devices.
Signed-off-by: Thara Gopinath
---
.../bindings/thermal/pwr-domain-warming.txt| 32 ++
1 file changed, 32 insertions(+)
create mode 100644
Resources modeled as power domains in linux kenrel
can be used to warm the SoC(eg. mx power domain on sdm845).
To support this feature, introduce a generic power domain
warming device driver that can be plugged into the thermal framework
(The thermal framework itself requires further modifiction
Add two new APIs in the genpd framework,
dev_pm_genpd_get_performance_state to return the current performance
state of a power domain and dev_pm_genpd_performance_state_count to
return the total number of performance states supported by a
power domain. Since the genpd framework does not maintain
a
RPMh hosts power domains that can be used to warm up the SoC.
Add nodes for these domains on sdm845 (mx power
domain).
Signed-off-by: Thara Gopinath
---
v1->v2:
- Change the dt-entries to reflect the newly introduced
generic power domain warming device.
Populate .get_performace_state_count in genpd ops to retrieve the count
of performance states supported by a rpmh power domain.
Signed-off-by: Thara Gopinath
---
v1->v2:
- Changes ti incorporate the new format of
get_performance_state_count.
drivers/soc/qcom/rpmhpd.c | 9
Certain resources modeled as a generic power domain in linux kernel
can be used to warm up the SoC (mx power domain on sdm845)
if the temperature falls below certain threshold. These power domains
can be considered as thermal warming devices.
(opposite of thermal cooling devices).
In kernel,
On 06/09/19 04:17, Peter Xu wrote:
> v4:
> - pick r-b
> - swap the last two patches [Sean]
>
> v3:
> - use unsigned int for vcpu id [Sean]
> - a new patch to fix ple_window type [Sean]
>
> v2:
> - fix commit messages, change format of ple window tracepoint [Sean]
> - rebase [Wanpeng]
>
> Each
On Sun, Aug 18, 2019 at 7:53 PM Colin King wrote:
>
> From: Colin Ian King
>
> Variable rc is initialized to a value that is never read and it
> is re-assigned later. The initialization is redundant and can be
> removed.
Applied to ntb-next, thanks
> Addresses-Coverity: ("Unused value")
>
This fixes 11da04af0d3b, as devm_gpiod_get_from_of_node() does
not do translation "con-id" -> "con-id-gpios" that our bindings expects,
and therefore it was wrong to change connection ID to be simply "enable"
when moving to using devm_gpiod_get_from_of_node().
Fixes: 11da04af0d3b ("regulator:
This fixes 96392c3d8ca4, as devm_gpiod_get_from_of_node() does
not do translation "con-id" -> "con-id-gpios" that our bindings expects,
and therefore it was wrong to change connection ID to be simply
"maxim,ena" when moving to using devm_gpiod_get_from_of_node().
Fixes: 96392c3d8ca4 ("regulator:
Hi Adam,
> Am 09.09.2019 um 21:13 schrieb Adam Ford :
>
> On Mon, Sep 9, 2019 at 1:11 PM H. Nikolaus Schaller
> wrote:
>>
>> Ok, we have to check if the ti,abb-v2 "LDO" driver
>> drivers/regulator/ti-abb-regulator.c
>> can handle that with a DT entry similar to:
>>
>>
On 9/10/2019 9:40 AM, Borislav Petkov wrote:
On Tue, Sep 10, 2019 at 08:34:44AM -0700, Mike Travis wrote:
Hi, I'm not conscientiously adding any attachments. I think what is
happening is some email readers mistake the '---' to signify an attachment
follows. I see the "staple" symbol on
On Wed, Sep 4, 2019 at 5:53 PM Daniel Colascione wrote:
>
> A task with CAP_SYS_ADMIN can mark itself PR_SET_TASK_CRITICAL,
> meaning that if the task ever exits, the kernel panics. This facility
> is intended for use by low-level core system processes that cannot
> gracefully restart without a
From: Jose Abreu
Date: Sep/10/2019, 15:41:21 (UTC+00:00)
> Misc patches for -next. It includes:
> - Two fixes for features in -next only
> - New features support for GMAC cores (which includes GMAC4 and GMAC5)
BTW, just for reference (and because I forgot to attach it earlier),
this is the
On Tue, Sep 10, 2019 at 06:55:07PM +0300, tinywrkb wrote:
> Cubox-i Solo/DualLite carrier board has 100Mb/s magnetics while the
That statement is false, sorry. All boards support 1G.
> Atheros AR8035 PHY on the MicroSoM v1.3 CPU module is a 1GbE PHY device.
>
> Since commit 5502b218e001 ("net:
On Sun, Sep 08, 2019 at 05:40:41PM +0300, Ivan Safonov wrote:
> Resolve TODO:
> > The following two functions "fix" the issue where there are more pids
> > than kmalloc will give memory for; in such cases, we use vmalloc/vfree.
> > TODO: replace with a kernel-wide solution to this problem
>
>
On Wed, Apr 10, 2019 at 11:24 AM Mehta, Sanju wrote:
>
> Hi All,
>
> Any comments on below patch?
I wasn't cc'ed, so this one missed my inbox. Applied to ntb-next, thanks.
>
> Thanks & Regards,
> Sanjay Mehta
>
> -Original Message-
> From: Mehta, Sanju
> Sent: Friday, March 29, 2019
On Tue, Sep 10, 2019 at 08:34:44AM -0700, Mike Travis wrote:
> Hi, I'm not conscientiously adding any attachments. I think what is
> happening is some email readers mistake the '---' to signify an attachment
> follows. I see the "staple" symbol on some indicating an attachment, but
> not
We can simply store the pages in a list (page->lru), no need for a
separate data structure (+ complicated handling). This is how most
other balloon drivers store allocated pages without additional tracking
data.
For the notifiers, use page_to_pfn() to check if a page is in the
applicable range.
On Tuesday 10 September 2019 11:21:34 Adam Ford wrote:
> According to a note in omap_hwmod_3xxx_data.c,
>
> /*
> * Apparently the SHA/MD5 and AES accelerator IP blocks are
> * only present on some AM35xx chips, and no one knows which
> * ones. See
> *
Hello, maintainers.
If you are available, please review this patch and share the feedback.
Thanks,
Austin Kim
2019년 9월 3일 (화) 오후 12:30, Austin Kim 님이 작성:
>
> gcc throws warning message as below:
>
> ‘clone_src_i_size’ may be used uninitialized in this function
> [-Wmaybe-uninitialized]
>
arch/powerpc/kernel/ contains 8 files dedicated to kexec.
Move them into a dedicated subdirectory.
Signed-off-by: Christophe Leroy
---
v2: moved crash.c as well as it's part of kexec suite.
v3: renamed files to remove 'kexec' keyword from names.
---
arch/powerpc/kernel/Makefile
Almost half of misc_32.S is dedicated to kexec.
That's the relocation function for kexec.
Drop it into a dedicated kexec_relocate_32.S
Signed-off-by: Christophe Leroy
---
v2: no change
v3: renamed kexec_32.S to kexec_relocate_32.S
---
arch/powerpc/kernel/Makefile| 1 +
On 10.09.19 18:18, Dr. David Alan Gilbert wrote:
> * Alexander Duyck (alexander.du...@gmail.com) wrote:
>> On Tue, Sep 10, 2019 at 7:47 AM Michal Hocko wrote:
>>>
>>> On Tue 10-09-19 07:42:43, Alexander Duyck wrote:
On Tue, Sep 10, 2019 at 5:42 AM Michal Hocko wrote:
>
> I wanted to
On Tue, 10 Sep 2019 at 19:59, Andrew Murray wrote:
>
> On Tue, Sep 10, 2019 at 05:55:02PM +0530, Pankaj Dubey wrote:
> > From: Anvesh Salveru
> >
> > In some platforms, PCIe PHY may have issues which will prevent linkup
> > to happen in GEN3 or high speed. In case equalization fails, link will
>
On Tue, Sep 10, 2019 at 10:48 AM Adam Ford wrote:
>
> On Mon, Sep 9, 2019 at 11:35 AM Tony Lindgren wrote:
> >
> > * Pali Rohár [190909 13:41]:
> > > On Monday 09 September 2019 08:37:09 Adam Ford wrote:
> > > > I applied this on 5.3 and it is working. I assume the same is true in
> > > >
Hans Verkuil wrote on Tue [2019-Sep-10 12:42:51 +0200]:
> Hi Benoit,
>
> On 9/9/19 6:27 PM, Benoit Parrot wrote:
> > This patch series is a collection of patches we have been carrying for a
> > while.
> >
> > A few patches do fix actual bug and v4l2-compliance errors/warnings.
> > Other are
* Alexander Duyck (alexander.du...@gmail.com) wrote:
> On Tue, Sep 10, 2019 at 7:47 AM Michal Hocko wrote:
> >
> > On Tue 10-09-19 07:42:43, Alexander Duyck wrote:
> > > On Tue, Sep 10, 2019 at 5:42 AM Michal Hocko wrote:
> > > >
> > > > I wanted to review "mm: Introduce Reported pages" just
On Tue, Sep 03, 2019 at 03:15:58PM +0530, Anshuman Khandual wrote:
> @@ -770,6 +1022,28 @@ int __meminit vmemmap_populate(unsigned long start,
> unsigned long end, int node,
> void vmemmap_free(unsigned long start, unsigned long end,
> struct vmem_altmap *altmap)
> {
> +#ifdef
Hi tinywrkb,
On Tue, Sep 10, 2019 at 06:55:07PM +0300, tinywrkb wrote:
> Cubox-i Solo/DualLite carrier board has 100Mb/s magnetics while the
> Atheros AR8035 PHY on the MicroSoM v1.3 CPU module is a 1GbE PHY device.
According to the hardware designer, Rabeeh Khoury, there is not such
limitation
On Tue, 10 Sep 2019 at 19:56, Andrew Murray wrote:
>
> On Tue, Sep 10, 2019 at 05:55:01PM +0530, Pankaj Dubey wrote:
> > From: Anvesh Salveru
> >
> > In some platforms, PCIe PHY may have issues which will prevent linkup
> > to happen in GEN3 or high speed. In case equalization fails, link will
>
Adding Jon and Baruch
On Tue, Sep 10, 2019 at 12:55 PM tinywrkb wrote:
>
> Cubox-i Solo/DualLite carrier board has 100Mb/s magnetics while the
> Atheros AR8035 PHY on the MicroSoM v1.3 CPU module is a 1GbE PHY device.
>
> Since commit 5502b218e001 ("net: phy: use phy_resolve_aneg_linkmode in
>
> On Sep 5, 2019, at 8:24 AM, Christoph Hellwig wrote:
>
>> On Thu, Sep 05, 2019 at 05:21:24PM +0200, Thomas Hellström (VMware) wrote:
>>> On 9/5/19 4:15 PM, Dave Hansen wrote:
>>> Hi Thomas,
>>>
>>> Thanks for the second batch of patches! These look much improved on all
>>> fronts.
>>
>>
Sometimes we have memories that are supposed to be read-only, but when
we map these regions the best we can do is map them as write-back with
MEMREMAP_WB. Introduce a read-only memory mapping (MEMREMAP_RO) that
allows us to map reserved memory regions as read-only. This way, we're
less likely to
We have a few drivers that need to get a reserved memory region, request
the region, and map the reserved memory with memremap(). Add an API to
do this all in one function call.
Cc: Evan Green
Cc: Rob Herring
Cc: Bjorn Andersson
Cc: Andy Gross
Cc: Will Deacon
Cc: Catalin Marinas
Cc: Dan
This gets rid of some duplicate code, and also makes the reserved memory
region show up as 'cmd-db' memory in /proc/iomem.
Cc: Evan Green
Cc: Rob Herring
Cc: Bjorn Andersson
Cc: Andy Gross
Cc: Will Deacon
Cc: Catalin Marinas
Cc: Dan Williams
Reviewed-by: Bjorn Andersson
Signed-off-by:
This patch series implements a read-only version of memremap() via
a new MEMREMAP_RO flag. If this is passed in the mapping call, we'll
try to map the memory region as read-only if it doesn't intersect
with an existing mapping. Otherwise, we'll try to fallback to other
flags to try to map the
Pass in PAGE_KERNEL_RO to the underlying IO mapping mechanism to get a
read-only mapping for the MEMREMAP_RO type of memory mappings that
memremap() supports.
Cc: Evan Green
Cc: Rob Herring
Cc: Bjorn Andersson
Cc: Andy Gross
Cc: Will Deacon
Cc: Catalin Marinas
Cc: Dan Williams
Reviewed-by:
The command DB is read-only already to the kernel because everything is
const marked once we map it. Let's go one step further and try to map
the memory as read-only in the page tables. This should make it harder
for random code to corrupt the database and change the contents.
Cc: Evan Green
Cc:
On 09/10/2019 05:00 AM, Kirill A. Shutemov wrote:
> On Mon, Sep 09, 2019 at 11:28:04AM -0500, Mike Christie wrote:
>> There are several storage drivers like dm-multipath, iscsi, and nbd that
>> have userspace components that can run in the IO path. For example,
>> iscsi and nbd's userspace deamons
On Tue, Sep 10, 2019 at 7:47 AM Michal Hocko wrote:
>
> On Tue 10-09-19 07:42:43, Alexander Duyck wrote:
> > On Tue, Sep 10, 2019 at 5:42 AM Michal Hocko wrote:
> > >
> > > I wanted to review "mm: Introduce Reported pages" just realize that I
> > > have no clue on what is going on so returned to
Hi Sheetal,
Some comments inline.
On 2019-09-10 8:17 a.m., Sheetal Tigadoli wrote:
From: Vikas Gupta
This driver registers on TEE bus to interact with OP-TEE based
BNXT firmware management modules
Signed-off-by: Vikas Gupta
Signed-off-by: Sheetal Tigadoli
---
Hi Thara,
Thanks for the review. Please find replies below.
On Thu, Aug 29, 2019 at 9:23 AM Thara Gopinath
wrote:
>
> Hi Amit,
>
> On 08/27/2019 08:14 AM, Amit Kucheria wrote:
> > Depending on the IP version, TSENS supports upper, lower, max, min and
> > critical threshold interrupts. We only
Hi Linus,
This is a resend of the pull request for v5.4 with the clone3 extension for
choosing a specific pid at process creation time _dropped_: After an
in-person discussion between multiple parties at LPC/KSummit use-cases were
presented that require restoring nested pid namespaces. This means
Cubox-i Solo/DualLite carrier board has 100Mb/s magnetics while the
Atheros AR8035 PHY on the MicroSoM v1.3 CPU module is a 1GbE PHY device.
Since commit 5502b218e001 ("net: phy: use phy_resolve_aneg_linkmode in
genphy_read_status") ethernet is broken on Cubox-i Solo/DualLite devices.
This adds
Convert Samsung Exynos IOMMU H/W, System Memory Management Unit
to newer dt-schema format.
Update clock description.
Signed-off-by: Maciej Falkowski
Signed-off-by: Andrzej Hajda
---
Hi Krzysztof,
Thank you for feedback.
New changes:
- style fixes including missing empty lines,
deletion of
From: rain.1986.08...@gmail.com
Date: Sat, 7 Sep 2019 16:14:46 +0800
> From: Rain River
>
> Many FORCEDETH NICs are used in our hosts. Several bugs are fixed and
> some features are developed for FORCEDETH NICs. And I have been
> reviewing patches for FORCEDETH NIC for several months. Mark me
On Mon, Sep 9, 2019 at 11:35 AM Tony Lindgren wrote:
>
> * Pali Rohár [190909 13:41]:
> > On Monday 09 September 2019 08:37:09 Adam Ford wrote:
> > > I applied this on 5.3 and it is working. I assume the same is true in
> > > for-next.
>
> Hmm I noticed I stopped getting RNG data after several
On Mon, Sep 09, 2019 at 10:59:40AM +0300, Felipe Balbi wrote:
> /*
> * Bits of the ptp_perout_request.flags field:
> */
> -#define PTP_PEROUT_VALID_FLAGS (~0)
> -
> +#define PTP_PEROUT_ONE_SHOT (1<<0)
> +#define PTP_PEROUT_VALID_FLAGS (~PTP_PEROUT_ONE_SHOT)
Here also, the bitwise not
Alex,
On 8/28/19 2:37 PM, Graf (AWS), Alexander wrote:
@@ -5522,9 +5558,6 @@ static void enable_irq_window(struct kvm_vcpu
*vcpu)
{
struct vcpu_svm *svm = to_svm(vcpu);
-if (kvm_vcpu_apicv_active(vcpu))
-return;
-
/*
From: David Miller
Date: Tue, 10 Sep 2019 17:45:44 +0200 (CEST)
> From: Alexandru Ardelean
> Date: Fri, 6 Sep 2019 15:30:54 +0300
>
>> The socfpga sub-driver defines an `interface` field in the `socfpga_dwmac`
>> struct and parses it on init.
>>
>> The shared `stmmac_probe_config_dt()`
On Tue, Sep 10, 2019 at 5:10 PM Stephen Rothwell wrote:
>
> Hi all,
>
> In commit
>
> e83dd16c24d8 ("fix compat handling of FICLONERANGE, FIDEDUPERANGE and
> FS_IOC_FIEMAP")
>
> Fixes tag
>
> Fixes: d79bdd52d8be7 54dbc15172375 ceac204e1da94
>
> has these problem(s):
>
> - Subject does not
From: Alexandru Ardelean
Date: Fri, 6 Sep 2019 15:30:54 +0300
> The socfpga sub-driver defines an `interface` field in the `socfpga_dwmac`
> struct and parses it on init.
>
> The shared `stmmac_probe_config_dt()` function also parses this from the
> device-tree and makes it available on the
On Tue, Sep 10, 2019 at 8:01 AM Robin Murphy wrote:
>
> On 07/09/2019 18:50, Rob Clark wrote:
> > From: Rob Clark
> >
> > When games, browser, or anything using a lot of GPU buffers exits, there
> > can be many hundreds or thousands of buffers to unmap and free. If the
> > GPU is otherwise
On Mon, Sep 09, 2019 at 10:59:39AM +0300, Felipe Balbi wrote:
> case PTP_PEROUT_REQUEST:
> + case PTP_PEROUT_REQUEST2:
...
> + if (((req.perout.flags & ~PTP_PEROUT_VALID_FLAGS) ||
> + req.perout.rsv[0] || req.perout.rsv[1] ||
> +
From: Arnd Bergmann
> Sent: 10 September 2019 09:15
...
> > I am not sure how this would work, since the format parameters can
> > changes depending on the FW string and the specific traces.
>
> Ah, so the format string comes from the firmware? I didn't look
> at the code in enough detail to
On 9/10/2019 5:07 AM, Miguel Ojeda wrote:
On Thu, Sep 5, 2019 at 3:50 PM Mike Travis wrote:
These patches support upcoming UV systems that do not have a UV HUB.
Please send patches as plain text without attachments. See:
The Xylon LogiCVC display controller exports some GPIOs, which are
exposed as a dedicated driver.
This introduces the associated device-tree bindings documentation.
Signed-off-by: Paul Kocialkowski
---
.../bindings/gpio/xylon,logicvc-gpio.txt | 48 +++
1 file changed, 48
The LogiCVC display hardware block comes with GPIO capabilities
that must be exposed separately from the main driver (as GPIOs) for
use with regulators and panels. A syscon is used to share the same
regmap across the two drivers.
Since the GPIO capabilities are pretty simple, add them to the
Some drivers might need a custom get operation to match custom
behavior implemented in the set operation.
Add plumbing for supporting that.
Signed-off-by: Paul Kocialkowski
---
drivers/gpio/gpio-syscon.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git
>
> On Tue, Sep 10, 2019 at 03:42:15PM +0100, Jarkko Sakkinen wrote:
> > On Mon, Sep 09, 2019 at 06:09:06PM +0900, Seunghun Han wrote:
> > > I got an AMD system which had a Ryzen Threadripper 1950X and MSI
> > > mainboard, and I had a problem with AMD's fTPM. My machine showed an error
> > >
On 9/10/19 8:48 AM, Tim Sander wrote:
> Hi
>
> I have noticed that my SPF records where not in place after moving the server,
> so it seems the mail didn't go to the mailing list. Hopefully that's fixed
> now.
>
> Am Dienstag, 10. September 2019, 09:16:37 CEST schrieb Masahiro Yamada:
>> On
On Thu, 2019-09-05 at 17:08 -0400, Qian Cai wrote:
> Another data point is if change CONFIG_DEBUG_OBJECTS_TIMERS from =y to =n, it
> will also fix it.
>
> On Thu, 2019-08-22 at 17:33 -0400, Qian Cai wrote:
> > https://raw.githubusercontent.com/cailca/linux-mm/master/arm64.config
> >
> > Booting
Check that the time received from the RTC HW is valid,
otherwise the computation of rtc_year_days() in the next
line could, and sometimes does, crash the kernel.
While we're at it, fix the license to plain "GPL".
Signed-off-by: Nick Crews
---
drivers/rtc/rtc-wilco-ec.c | 12 ++--
1
On Tue, Sep 10, 2019 at 04:46:15PM +0200, Christian Brauner wrote:
> On Tue, Sep 10, 2019 at 04:39:44PM +0200, Oleg Nesterov wrote:
> > On 09/10, Christian Brauner wrote:
> > > On Tue, Sep 10, 2019 at 03:10:48PM +0200, Christian Brauner wrote:
> > > > On Tue, Sep 10, 2019 at 03:09:35PM +0200,
From: Vikas Gupta
This driver registers on TEE bus to interact with OP-TEE based
BNXT firmware management modules
Signed-off-by: Vikas Gupta
Signed-off-by: Sheetal Tigadoli
---
drivers/firmware/broadcom/Kconfig | 8 +
drivers/firmware/broadcom/Makefile| 1 +
On 09/09/2019 15:30:31+, eugen.hris...@microchip.com wrote:
> From: Eugen Hristev
>
> The regmap update bits call was not selecting the proper mask, considering
> the bits which was updating.
> Update the mask from call to also include OSCBYPASS.
> Removed MOSCEN which was not updated.
>
>
On 09/09/2019 14:00:35+0300, Claudiu Beznea wrote:
> From: Sandeep Sheriker Mallikarjun
>
> Add support for SAM9X60 irqchip.
>
> Signed-off-by: Sandeep Sheriker Mallikarjun
>
> [claudiu.bez...@microchip.com: update aic5_irq_fixups[], update
> documentation]
> Signed-off-by: Claudiu Beznea
>
> On Mon, Sep 09, 2019 at 06:09:05PM +0900, Seunghun Han wrote:
> > The purpose of crb_fixup_cmd_size() function is to work around broken
> > BIOSes and get the trustable size between the ACPI region and register.
> > When the TPM has a command buffer and response buffer independently,
> > the
From: Stefan Hajnoczi
Add a basic file system module for virtio-fs. This does not yet contain
shared data support between host and guest or metadata coherency speedups.
However it is already significantly faster than virtio-9p.
Design Overview
===
With the goal of designing
From: "Michael S. Tsirkin"
virtio fs tunnels fuse over a virtio channel. One issue is two sides might
be speaking different endian-ness. To detects this, host side looks at the
opcode value in the FUSE_INIT command. Works fine at the moment but might
fail if a future version of fuse will use
On Tue, Sep 10, 2019 at 02:55:27PM +, Christophe Leroy wrote:
> arch/powerpc/kernel/ contains 7 files dedicated to kexec.
>
> Move them into a dedicated subdirectory.
> arch/powerpc/kernel/{ => kexec}/ima_kexec.c| 0
> arch/powerpc/kernel/{ => kexec}/kexec_32.S | 2 +-
>
From: Stefan Hajnoczi
Add information about the new "virtiofs" file system.
Signed-off-by: Stefan Hajnoczi
Signed-off-by: Miklos Szeredi
---
Documentation/filesystems/index.rst| 10 +
Documentation/filesystems/virtiofs.rst | 60 ++
MAINTAINERS
From: "Dr. David Alan Gilbert"
SETUPMAPPING is a command for use with 'virtiofsd', a fuse-over-virtio
implementation; it may find use in other fuse impelementations as well in
which the kernel does not have access to the address space of the daemon
directly.
A SETUPMAPPING operation causes a
Git tree for this version is available here:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git#virtiofs-v5
Only post patches that actually add virtiofs (virtiofs-v5-base..virtiofs-v5).
I've folded the series from Vivek and fixed a couple of TODO comments
myself. AFAICS two issues
On Tue Sep 10 19, Jarkko Sakkinen wrote:
The chip is not released when the validation for @digests fails. Add
tpm_put_ops() to the failure path.
Cc: sta...@vger.kernel.org
Reported-by: Roberto Sassu
Signed-off-by: Jarkko Sakkinen
Reviewed-by: Jerry Snitselaar
---
Hi all,
In commit
e83dd16c24d8 ("fix compat handling of FICLONERANGE, FIDEDUPERANGE and
FS_IOC_FIEMAP")
Fixes tag
Fixes: d79bdd52d8be7 54dbc15172375 ceac204e1da94
has these problem(s):
- Subject does not match target commit subject
Just use
git log -1 --format='Fixes: %h
On Tue, Sep 10, 2019 at 03:42:15PM +0100, Jarkko Sakkinen wrote:
> On Mon, Sep 09, 2019 at 06:09:06PM +0900, Seunghun Han wrote:
> > I got an AMD system which had a Ryzen Threadripper 1950X and MSI
> > mainboard, and I had a problem with AMD's fTPM. My machine showed an error
> > message below,
Hi Sakari,
On 10/09/19 10:43, Sakari Ailus wrote:
> Hi Luca,
>
> On Tue, Jul 23, 2019 at 10:37:20PM +0200, Luca Ceresoli wrote:
>
> ...
>
>> +Device node example
>> +---
>> +
>> + {
>> +deser: deser@3d {
>> +compatible = "ti,ds90ub954-q1";
>> +
Indicate to UV user utilities that UV hubless support is available on
this system via the existing /proc infterface. The current interface is
maintained with the addition of new /proc leaves ("hubbed", "hubless",
and "oemid") that contain the specific type of UV arch this one is.
Signed-off-by:
Add a return code to the UV BIOS init function that indicates the
successful initialization of the kernel/BIOS callback interface.
Signed-off-by: Mike Travis
Reviewed-by: Steve Wahl
Reviewed-by: Dimitri Sivanich
---
arch/x86/include/asm/uv/bios.h |2 +-
arch/x86/platform/uv/bios_uv.c |
Return the type of UV hubless system for UV specific code that depends
on that. Add a function to convert UV system type to bit pattern needed
for is_uv_hubless().
Signed-off-by: Mike Travis
Reviewed-by: Steve Wahl
Reviewed-by: Dimitri Sivanich
---
V2: Remove is_uv_hubless define
Remove
Decode the hubless UVsystab passed from BIOS to the kernel saving
pertinent info in a similar manner that hubbed UVsystabs are decoded.
Signed-off-by: Mike Travis
Reviewed-by: Steve Wahl
Reviewed-by: Dimitri Sivanich
---
V2: Removed redundant error message after call to uv_bios_init.
Add more support for UV systems that do not contain a UV Hub (AKA
"hubless"). This update adds support for additional functions required:
Use PCH NMI handler instead of a UV Hub NMI handler.
Initialize the UV BIOS callback interface used to support specific
UV functions.
Save the OEM_ID and OEM_TABLE_ID passed to the apic driver probe function
for later use. Also, convert the char list arg passed from the kernel
to a true null-terminated string.
Signed-off-by: Mike Travis
Reviewed-by: Steve Wahl
Reviewed-by: Dimitri Sivanich
---
Change to checking for EFI Boot type from previous check on if this
is a KDUMP kernel. This allows for KDUMP kernels that can handle
EFI reboots.
Signed-off-by: Mike Travis
Reviewed-by: Steve Wahl
Reviewed-by: Dimitri Sivanich
---
arch/x86/kernel/apic/x2apic_uv_x.c | 18 --
On 9/5/2019 11:47 AM, Mike Travis wrote:
>
> These patches support upcoming UV systems that do not have a UV HUB.
>
> [1/8] Save OEM_ID from ACPI MADT probe
>
> [2/8] Return UV Hubless System Type
V2: Remove is_uv_hubless define
Remove leading '_' from _is_uv_hubless
> [3/8] Add
The references in the is_uvX_hub() function uses the hub_info pointer
which will be NULL when the system is hubless. This change avoids
that NULL dereference. It is also an optimization in performance.
Signed-off-by: Mike Travis
Reviewed-by: Steve Wahl
Reviewed-by: Dimitri Sivanich
---
V2:
Hi all,
In commit
8776f3fa15a5 ("io_uring: fix wrong sequence setting logic")
Fixes tag
Fixes: de0617e4671 ("io_uring: add support for marking commands as draining")
has these problem(s):
- SHA1 should be at least 12 digits long
Can be fixed by setting core.abbrev to 12 (or more)
Almost half of misc_32.S is dedicated to kexec.
Drop it into a dedicated kexec_32.S
Signed-off-by: Christophe Leroy
---
v2: no change
---
arch/powerpc/kernel/Makefile | 1 +
arch/powerpc/kernel/kexec_32.S | 500 +
arch/powerpc/kernel/misc_32.S |
arch/powerpc/kernel/ contains 7 files dedicated to kexec.
Move them into a dedicated subdirectory.
Signed-off-by: Christophe Leroy
---
v2: moved crash.c as well as it's part of kexec suite.
---
arch/powerpc/kernel/Makefile | 19 +---
On Tue, Sep 10, 2019 at 01:46:48PM +0300, Sergei Shtylyov wrote:
Hello!
On 10.09.2019 13:38, Ivan Khoronzhuk wrote:
echo should be replaced on echo -e to handle \n correctly, but instead,
s/on/with/?
s/echo/printf/ instead of s/echo/echo -e/
printf looks better.
replace it on printf
On Tue, Sep 10, 2019 at 7:01 AM Michal Hocko wrote:
>
> On Fri 06-09-19 08:09:52, Toshiki Fukasawa wrote:
> [...]
> > @@ -5856,8 +5855,6 @@ void __meminit memmap_init_zone(unsigned long size,
> > int nid, unsigned long zone,
> > if (!altmap)
> > return;
> >
>
Quoting Mars Cheng (2019-08-19 02:21:41)
> From: mtk01761
>
> Add MT6779 clock support, include topckgen, apmixedsys,
> infracfg, and subsystem clocks.
>
> Signed-off-by: mtk01761
> ---
Applied to clk-next
201 - 300 of 833 matches
Mail list logo
