The following changes since commit 9f9499ae8e6415cefc4fe0a96ad0e27864353c89:
Linux 4.4-rc5 (2015-12-13 17:42:58 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus
for you to fetch changes up to 74a599f09bec7419b2490039f0
From: Namhyung Kim
Currently trace-cmd prints ring buffer events in a strict time order.
But it sometimes annoying that stacktrace from the same cpu can be
intermixed with events from other cpu. This patch looks next event when
print last record and prints it also if it's a stacktrace (from the
On Fri, Dec 11, 2015 at 01:36:26PM +, Mans Rullgard wrote:
> Add auart4 2-pin configuration on auart0 rts/cts pads.
>
> Signed-off-by: Mans Rullgard
Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.o
Hi Mark,
On 12/21/2015 03:31 PM, Mark yao wrote:
On 2015年11月11日 15:46, Yakir Yang wrote:
+hdmi->connector.polled = DRM_CONNECTOR_POLL_HPD;
+
+drm_connector_helper_add(&hdmi->connector,
+ &inno_hdmi_connector_helper_funcs);
+drm_connector_init(drm, &hdmi->connector,
Hi Mark
On 12/21/2015 03:25 PM, Mark yao wrote:
Hi Yakir
I want to convert drm/rockchip to support atomic api,
I'd like you can do some modify to adapt it.
Sure, would update as soon as possible.
Thanks,
- Yakir
- Mark
On 2015年11月11日 15:45, Yakir Yang wrote:
Hi guys:
Here are a
On 12/19/2015 03:28 AM, KY Srinivasan wrote:
[ .. ]
Could you? You're making what you describe as an optimisation but
there are two reasons why this might not be so. The first is that the
compiler is entitled to inline static functions. If it did, likely it
picked up the optmisation anyway
On Sun, Dec 20, 2015 at 09:34:29PM +0100, Maciej S. Szmigiero wrote:
> fsl_ssi uses different stream names ("AC97 Playback" / "AC97 Capture")
> in AC'97 mode so in this case fsl-asoc-card route map should
> also be using them.
>
> Signed-off-by: Maciej S. Szmigiero
Acked-by: Nicolin Chen
> ---
This patch is based on [PATCH] lightnvm: fix bio submission issue
https://lkml.org/lkml/2015/12/9/394
2015-12-21 15:32 GMT+08:00 Wenwei Tao :
> after io submission failed, before free rq, delete rq from
> rrpc's inflight list, leave no bad item in the list. And
> free rq's ppa_list to avoid memor
On Sun, Dec 20, 2015 at 12:15:50PM +0100, Julia Lawall wrote:
> Add NULL test on call to devm_kzalloc.
>
> The semantic match that finds this problem is as follows:
> (http://coccinelle.lip6.fr/)
>
> //
> @@
> expression x;
> @@
>
> * x = devm_kzalloc(...);
> ... when != x == NULL
> *x
> //
after io submission failed, before free rq, delete rq from
rrpc's inflight list, leave no bad item in the list. And
free rq's ppa_list to avoid memory leak.
Signed-off-by: Wenwei Tao
---
drivers/lightnvm/rrpc.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/lightnvm/rrpc.c b/d
On 2015-12-21 10:23, Linus Torvalds wrote:
On Sun, Dec 20, 2015 at 8:47 PM, Linus Torvalds
wrote:
That said, we obviously need to figure out this current problem
regardless first..
... although maybe it *would* be interesting to hear what happens if
you just compile a 64-bit kernel instead?
On 2015年11月11日 15:46, Yakir Yang wrote:
+ hdmi->connector.polled = DRM_CONNECTOR_POLL_HPD;
+
+ drm_connector_helper_add(&hdmi->connector,
+&inno_hdmi_connector_helper_funcs);
+ drm_connector_init(drm, &hdmi->connector, &inno_hdmi_connector_funcs,
Hi Yakir
I want to convert drm/rockchip to support atomic api,
I'd like you can do some modify to adapt it.
- Mark
On 2015年11月11日 15:45, Yakir Yang wrote:
Hi guys:
Here are a brief introduction to Innosilicon HDMI IP:
- Support HDMI 1.4a, HDCP 1.2 and DVI 1.0 standard compliant trans
On 2015-12-21 11:55, Tejun Heo wrote:
Artem, can you please reproduce the issue with the following patch
applied and attach the kernel log?
Thanks.
I've applied this patch on top of vanilla 4.3.3 kernel (without Linus'es
revert). Hopefully it's how you intended it to be.
Here's the result
At -Os, ARC gcc generates millicode thunk for function prologue/epilogue,
which are served by libgcc.
Modules historically are NOT linked with libgcc to avoid code bloat, reducing
runtime relocation fixups etc. I even once tried doign that but got lost
in makefile intricacies.
However CONFIG_MODU
On some architectures smp_store_mb() calls mb() which is stronger
than implied by both the name and the documentation.
smp_store_mb is only used by core kernel code at the moment, so
we know no one mis-uses it for an MMIO barrier.
Make it call smp_mb consistently before some arch-specific
code use
On Mon, Dec 21, 2015 at 03:00:08PM +0800, Zhu Guihua wrote:
>
> On 12/21/2015 11:15 AM, Joonsoo Kim wrote:
> >Hello, memory-hotplug folks.
> >
> >I found theoretical problems between memory hotplug and pfn iterator.
> >For example, pfn iterator works something like below.
> >
> >for (pfn = zone_st
Hi Andrew,
Today's linux-next merge of the akpm tree got a conflict in:
init/Kconfig
between commit:
6bf024e69333 ("cgroup: put controller Kconfig options in meaningful order")
from the cgroup tree and commit:
"mm: memcontrol: introduce CONFIG_MEMCG_LEGACY_KMEM"
from the akpm tree.
I
On Sun, Dec 20, 2015 at 08:59:44PM +0100, Peter Zijlstra wrote:
> On Sun, Dec 20, 2015 at 05:07:19PM +, Andrew Cooper wrote:
> >
> > Very much +1 for fixing this.
> >
> > Those names would be fine, but they do add yet another set of options in
> > an already-complicated area.
> >
> > An alte
On 17 December 2015 at 19:31, David Woods wrote:
> The arm64 MMU supports a Contiguous bit which is a hint that the TTE
> is one of a set of contiguous entries which can be cached in a single
> TLB entry. Supporting this bit adds new intermediate huge page sizes.
>
> The set of huge page sizes av
On 12/21/2015 11:15 AM, Joonsoo Kim wrote:
Hello, memory-hotplug folks.
I found theoretical problems between memory hotplug and pfn iterator.
For example, pfn iterator works something like below.
for (pfn = zone_start_pfn; pfn < zone_end_pfn; pfn++) {
if (!pfn_valid(pfn))
Artem, can you please reproduce the issue with the following patch
applied and attach the kernel log?
Thanks.
---
drivers/ata/libahci.c | 40 ++--
drivers/ata/libata-eh.c |4
drivers/ata/libata-scsi.c |1 +
3 files changed, 43 insertions(+
On Fri, Dec 18, 2015 at 11:06 PM, Yingjoe Chen
wrote:
> On Fri, 2015-12-18 at 12:21 +0800, Daniel Kurtz wrote:
>> Move pinctrl initialization earlier in boot so that real devices can find
>> their pctldev without probe deferring.
>>
>> Signed-off-by: Daniel Kurtz
>> ---
>> drivers/pinctrl/mediat
2015-12-05 14:17 GMT+08:00 Masahiro Yamada :
> The clk_disable() in the common clock framework (drivers/clk/clk.c)
> returns immediately if the given clk is NULL or an error pointer.
> It allows drivers to call clk_disable() (and clk_disable_unprepare())
> with a clock that might be NULL or an erro
On 2015/12/21 11:01, chenfeng wrote:
> Mark,
>
> On 2015/12/19 1:58, Mark Brown wrote:
>> On Thu, Dec 17, 2015 at 11:27:27AM +0800, chenfeng wrote:
>>
>>> +- regulator-vset-regs: Voltage set register offset.
>>> +- regulator-vset-mask: voltage set control mask.
>>> +- regulator-n-vol: The num
On multicore CPUs, sometimes debug console logs are not flushed
if you have VT consoles also enabled. Reason being console_lock
is taken by secondary/nonboot cpus which are disabled as part
of suspend.This patch flushes the console before disabling
nonboot cpus
Signed-off-by: Bibek Basu
---
ker
Hi Stephen Rothwell,
This is the same error what we discussed on Friday mail-chain. Please see the
attachment of my reply.
Regards,
Pramod
> -Original Message-
> From: Stephen Rothwell [mailto:s...@canb.auug.org.au]
> Sent: 21 December 2015 10:28
> To: Linus Walleij
> Cc: linux-n...@vge
On 12/20/2015 05:47 PM, Eric W. Biederman wrote:
Dongsheng Yang writes:
On 12/20/2015 10:37 AM, Al Viro wrote:
On Sun, Dec 20, 2015 at 10:14:29AM +0800, Dongsheng Yang wrote:
On 12/17/2015 07:23 PM, Dongsheng Yang wrote:
Hi guys,
We are working on making core dump behaviour isolated i
There is a performance drop report due to hugepage allocation and in there
half of cpu time are spent on pageblock_pfn_to_page() in compaction [1].
In that workload, compaction is triggered to make hugepage but most of
pageblocks are un-available for compaction due to pageblock type and
skip bit so
free_pfn and compact_cached_free_pfn are the pointer that remember
restart position of freepage scanner. When they are reset or invalid,
we set them to zone_end_pfn because freepage scanner works in reverse
direction. But, because zone range is defined as [zone_start_pfn,
zone_end_pfn), zone_end_pf
Move the stuff currently only used by the kexec file code within
CONFIG_KEXEC_FILE (and CONFIG_KEXEC_VERIFY_SIG).
Also move internal "struct kexec_sha_region" and "struct kexec_buf"
into "kexec_internal.h".
Signed-off-by: Xunlei Pang
---
arch/x86/kernel/machine_kexec_64.c | 2 ++
include/linux
hi,
I became maintainer for md (Linux Software RAID) in late 2001 and on
the whole it has been fun and a valuable experience. But I have been
losing interest in recent years (https://lwn.net/Articles/511073/) and
as was mentioned at the kernel summit, I would like to resign. Some
years ago
+++ Petr Mladek [17/12/15 16:45 +0100]:
On Wed 2015-12-16 00:40:48, Jessica Yu wrote:
Turns out the string parsing stuff, even with the help of lib/string.c, doesn't
look very pretty. As I'm working on v3, I'm starting to think having
klp_write_object_relocations() loop simply through all the el
Hi Brian,
After merging the l2-mtd tree, today's linux-next build (powerpc
ppc44x_defconfig) failed like this:
drivers/mtd/nand/ndfc.c: In function 'ndfc_chip_init':
drivers/mtd/nand/ndfc.c:177:2: error: 'ppdata' undeclared (first use in this
function)
ppdata.of_node = flash_np;
^
Caused by
+++ Petr Mladek [17/12/15 17:26 +0100]:
On Mon 2015-11-30 23:21:15, Jessica Yu wrote:
For livepatch modules, copy Elf section, symbol, and string information
from the load_info struct in the module loader.
Livepatch uses special relocation sections in order to be able to patch
modules that are
Hi Bjorn, can you comment on this. Marc has also replied for query on
irq_dispose_mapping().
> Subject: RE: [PATCH v11] PCI: Xilinx-NWL-PCIe: Added support for Xilinx NWL
> PCIe Host Controller
>
> > Subject: Re: [PATCH v11] PCI: Xilinx-NWL-PCIe: Added support for
> > Xilinx NWL PCIe Host Contro
On Sun, Dec 20, 2015 at 8:47 PM, Linus Torvalds
wrote:
>
> That said, we obviously need to figure out this current problem
> regardless first..
... although maybe it *would* be interesting to hear what happens if
you just compile a 64-bit kernel instead?
Do you still see the problem? Because if
On Sun, Dec 20, 2015 at 8:26 PM, Tejun Heo wrote:
>
> I wonder whether ahci is screwing up command / sg table setup in a way
> that e.g. if there are too many segments the sg table overflows into
> the neighboring one which is now being exposed by upper layer being
> fixed to send down larger comm
Hi Linus,
On Wed, 16 Dec 2015 14:37:55 +1100 Stephen Rothwell
wrote:
>
> After merging the gpio tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> drivers/pinctrl/bcm/pinctrl-nsp-gpio.c: In function 'nsp_gpio_probe':
> drivers/pinctrl/bcm/pinctrl-nsp-gpio.c:699:4: e
Hi Linus,
After merging the pinctrl tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
drivers/pinctrl/bcm/pinctrl-iproc-gpio.c:640:50: warning: 'struct cygnus_gpio'
declared inside parameter list
static void iproc_gpio_unregister_pinconf(struct cygnus_gpio *chip)
On Mon, Dec 21, 2015 at 03:41:19PM +1100, Stephen Rothwell wrote:
> Hi Tejun,
>
> Today's linux-next merge of the cgroup tree got a conflict in:
>
> init/Kconfig
>
> between commits:
>
> 257372262056 ("x86/intel_rdt: Add support for Cache Allocation detection")
> 5ad9144cdb9a ("x86,cgroup
On Sun, Dec 20, 2015 at 8:43 PM, Artem S. Tashkinov wrote:
>
> In the past I happily ran an x86_64 bit kernel together with 32bit userland
> for quite some time but then I hit a wall: VirtualBox expects its kernel
> modules to have the same bitness as the application itself so I had to
> revert ba
Kernel option COMPAT defines the ability of executing aarch32 binaries.
Some platforms does not support aarch32 mode, and so cannot execute that
binaries. But we cannot just disable COMPAT for them because the same
kernel binary may be used by multiple platforms.
In this patch, system_supports_aar
On 2015-12-21 09:32, Linus Torvalds wrote:
On Sun, Dec 20, 2015 at 5:50 PM, Artem S. Tashkinov wrote:
P.S. I know Linus doesn't condone PAE but I still find it more
preferrable
than running a mixed environment with almost zero benefit in regard to
performance and quite obvious performance reg
Hi Tejun,
Today's linux-next merge of the cgroup tree got a conflict in:
include/linux/cgroup_subsys.h
between commit:
5ad9144cdb9a ("x86,cgroup/intel_rdt : Add a cgroup interface to manage Intel
cache allocation")
from the tip tree and commit:
b53202e63089 ("cgroup: kill cgrp_ss_priv[
Hi Tejun,
Today's linux-next merge of the cgroup tree got a conflict in:
init/Kconfig
between commits:
257372262056 ("x86/intel_rdt: Add support for Cache Allocation detection")
5ad9144cdb9a ("x86,cgroup/intel_rdt : Add a cgroup interface to manage Intel
cache allocation")
from the tip
On Sun, Dec 20, 2015 at 5:50 PM, Artem S. Tashkinov wrote:
>
> P.S. I know Linus doesn't condone PAE but I still find it more preferrable
> than running a mixed environment with almost zero benefit in regard to
> performance and quite obvious performance regressions related to an
> increased numbe
Hello, Linus.
On Sun, Dec 20, 2015 at 09:51:14AM -0800, Linus Torvalds wrote:
...
> (Also Tejun - maybe you can see what's up - maybe that error message
> tells you something)
Hmmm... all it says is that something went wrong on the PCI side.
> I'm not sure what's up with his machine, the disk do
> On Dec 19, 2015, at 10:54, Minfei Huang wrote:
>
> The variant pagep will still get the invalid page point, although ceph
> fails in function ceph_update_writeable_page.
>
> To fix this issue, Assigne the page to pagep until there is no failure
> in function ceph_update_writeable_page.
>
> S
Hi Sascha,
One nit below that can be fixed up later, or now if you don't plan to
spin this driver to
address Eduardo's feedback...
On Mon, Nov 30, 2015 at 7:42 PM, Sascha Hauer wrote:
> This adds support for the Mediatek thermal controller found on MT8173
> and likely other SoCs.
> The controlle
On 2015-12-21 08:21, Ming Lei wrote:
On Mon, Dec 21, 2015 at 10:25 AM, Artem S. Tashkinov wrote:
# cat
/sys/block/sda/queue/{max_hw_sectors_kb,max_sectors_kb,max_segments,max_segment_size}
32767
32767
168
65536
Looks it is fine, then maybe it is related with
BIOVEC_PHYS_MERGEABLE(),
BIOVEC_S
On Mon, Dec 21, 2015 at 10:25 AM, Artem S. Tashkinov wrote:
> # cat
> /sys/block/sda/queue/{max_hw_sectors_kb,max_sectors_kb,max_segments,max_segment_size}
> 32767
> 32767
> 168
> 65536
Looks it is fine, then maybe it is related with BIOVEC_PHYS_MERGEABLE(),
BIOVEC_SEG_BOUNDARY() or sort of thing
On 19-12-15, 12:54, Javi Merino wrote:
> In __cpufreq_cooling_register() we allocate the arrays for time_in_idle
> and time_in_idle_timestamp to be as big as the number of cpus in this
> cpufreq device. However, in get_load() we access this array using the
> cpu number as index, which can result i
On 19-12-15, 09:23, SF Markus Elfring wrote:
> >> From: Markus Elfring
> >> Date: Fri, 18 Dec 2015 19:43:27 +0100
> >>
> >> The return type "unsigned long" was used by the cpu_set_cclk() function
> >> while the type "int" is provided by the clk_set_rate() function.
> >> Let us make this usage cons
From: Ma Jun
The current MSI framework can only support 256 platform MSIs.
But on Hisilicon platform, some network related devices has about 500
wired interrupts.
To support these devices, we need a new maximum value more than 256.
Signed-off-by: Ma Jun
---
drivers/base/platform-msi.c |2
Hello, memory-hotplug folks.
I found theoretical problems between memory hotplug and pfn iterator.
For example, pfn iterator works something like below.
for (pfn = zone_start_pfn; pfn < zone_end_pfn; pfn++) {
if (!pfn_valid(pfn))
continue;
page = pfn_to_page(pfn);
Hi Daniel,
Today's linux-next merge of the clockevents tree got a conflict in:
drivers/clocksource/h8300_timer16.c
between commit:
d33f250af4e6 ("clocksource/drivers/h8300: Use ioread / iowrite")
from the tip tree and commit:
1ddca16cc5b3 ("clocksource/drivers/h8300: Use ioread / iowrit
Mark,
On 2015/12/19 1:58, Mark Brown wrote:
> On Thu, Dec 17, 2015 at 11:27:27AM +0800, chenfeng wrote:
>
>> +- regulator-vset-regs: Voltage set register offset.
>> +- regulator-vset-mask: voltage set control mask.
>> +- regulator-n-vol: The num of support voltages.
>> +- regulator-vset-table
On 2015년 12월 21일 03:31, Sergei Shtylyov wrote:
> Some #include's weren't needed from the start, some are left overs from the
> earlier driver versions... Kill 'em all! :-)
I don't prefer following expression. I think you should write the description
to maintain the formal style on the next.
- "...
Hi,
On 2015년 12월 21일 02:15, Sergei Shtylyov wrote:
> Hello.
>
> On 12/20/2015 05:31 PM, Chanwoo Choi wrote:
>
>> This patch depend on GPIOLIB configuration as following:
>> I modified it with following diff and applied it.
>>
>> diff --git a/drivers/extcon/Kconfig b/drivers/extcon/Kconfig
>> ind
Hi Biao and Joe,
On Fri, Dec 18, 2015 at 11:13 PM, Yingjoe Chen
wrote:
> On Fri, 2015-12-11 at 17:07 +0800, Biao Huang wrote:
>> Add mt2701 support using mediatek common pinctrl driver.
>> MT2701 have some special pins need an extra setting register
>> than other ICs, so adding this support to co
On Thursday, December 10, 2015 08:55:30 AM Suravee Suthikulpanit wrote:
> This patch introduces gicv2m_acpi_init(), which uses information
> in MADT GIC MSI frames structure to initialize GICv2m driver.
> It also exposes gicv2m_init() function, which simplifies callers
> to a single GICv2m init fun
On Mon, Dec 21, 2015 at 06:50:21AM +0500, Artem S. Tashkinov wrote:
> On 2015-12-21 06:38, Ming Lei wrote:
> >On Mon, Dec 21, 2015 at 1:51 AM, Linus Torvalds wrote:
> >>Kent, Jens, Christoph et al,
> >> please see this bugzilla:
> >>
> >> https://bugzilla.kernel.org/show_bug.cgi?id=109661
> >>
> >
On Thursday, December 10, 2015 08:55:27 AM Suravee Suthikulpanit wrote:
> This patch introduces pci_msi_register_fwnode_provider() for irqchip
> to register a callback, to provide a way to determine appropriate MSI
> domain for a pci device.
>
> It also introduces pci_host_bridge_acpi_msi_domain()
On 2015-12-21 07:18, Ming Lei wrote:
On Mon, Dec 21, 2015 at 9:50 AM, Artem S. Tashkinov wrote:
BTW, I have posted very similar issue in the link:
http://marc.info/?l=linux-ide&m=145066119623811&w=2
Artem, I noticed from bugzillar that the hardware is i386, just
wondering if PAE is enabled? I
于 2015/12/20 8:25, Jan Stancek 写道:
> On Sat, Dec 19, 2015 at 11:04:21AM +0800, xiakaixu wrote:
>>
>...
>>>
>>> Hi,
>>>
>>> What is your objdump version?
>>
>> Hi,
>>
>> Sorry for the late reply.
>>
>> # objdump --version
>> GNU objdump (GNU Binutils) 2.25.
>>
>> I am sure that the system is
On Mon, Dec 21, 2015 at 9:50 AM, Artem S. Tashkinov wrote:
>> BTW, I have posted very similar issue in the link:
>>
>> http://marc.info/?l=linux-ide&m=145066119623811&w=2
>>
>> Artem, I noticed from bugzillar that the hardware is i386, just
>> wondering if PAE is enabled? If yes, I am more confid
On 2015/12/21 9:50, Wu, Feng wrote:
-Original Message-
From: Yang Zhang [mailto:yang.zhang...@gmail.com]
Sent: Monday, December 21, 2015 9:46 AM
To: Wu, Feng ; pbonz...@redhat.com;
rkrc...@redhat.com
Cc: k...@vger.kernel.org; linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] KVM
On 2015/12/21 9:55, Wu, Feng wrote:
-Original Message-
From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
ow...@vger.kernel.org] On Behalf Of Yang Zhang
Sent: Monday, December 21, 2015 9:50 AM
To: Wu, Feng ; pbonz...@redhat.com;
rkrc...@redhat.com
Cc: k...@vger.kernel.org;
> -Original Message-
> From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
> ow...@vger.kernel.org] On Behalf Of Yang Zhang
> Sent: Monday, December 21, 2015 9:50 AM
> To: Wu, Feng ; pbonz...@redhat.com;
> rkrc...@redhat.com
> Cc: k...@vger.kernel.org; linux-kernel@vger.kernel.
There are two version scale control register found on vop,
scale full version found on rk3288, support extension registers.
and scale little version found on rk3036, only support common scale.
Signed-off-by: Mark Yao
---
Changes in v1.1
- fix scale calculation mistake.
drivers/gpu/drm/rockchip/
> -Original Message-
> From: Yang Zhang [mailto:yang.zhang...@gmail.com]
> Sent: Monday, December 21, 2015 9:46 AM
> To: Wu, Feng ; pbonz...@redhat.com;
> rkrc...@redhat.com
> Cc: k...@vger.kernel.org; linux-kernel@vger.kernel.org
> Subject: Re: [PATCH v2 1/2] KVM: x86: Use vector-hashing
On 2015/12/16 9:37, Feng Wu wrote:
Use vector-hashing to deliver lowest-priority interrupts for
VT-d posted-interrupts.
Signed-off-by: Feng Wu
---
arch/x86/kvm/lapic.c | 67
arch/x86/kvm/lapic.h | 2 ++
arch/x86/kvm/vmx.c | 12
On 2015-12-21 06:38, Ming Lei wrote:
On Mon, Dec 21, 2015 at 1:51 AM, Linus Torvalds wrote:
Kent, Jens, Christoph et al,
please see this bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=109661
where Artem Tashkinov bisected his problems with 4.3 down to commit
b54ffb73cadc ("block: rem
On 2015/12/16 9:37, Feng Wu wrote:
Use vector-hashing to deliver lowest-priority interrupts, As an
example, modern Intel CPUs in server platform use this method to
handle lowest-priority interrupts.
Signed-off-by: Feng Wu
---
arch/x86/kvm/irq_comm.c | 27 ++-
arch/x86/kvm
On Mon, Dec 21, 2015 at 1:51 AM, Linus Torvalds
wrote:
> Kent, Jens, Christoph et al,
> please see this bugzilla:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=109661
>
> where Artem Tashkinov bisected his problems with 4.3 down to commit
> b54ffb73cadc ("block: remove bio_get_nr_vecs()") tha
Hi Robin,
On Friday 18 December 2015 20:20:56 Robin Murphy wrote:
> On 18/12/15 18:55, Doug Anderson wrote:
> > On Fri, Dec 18, 2015 at 4:41 AM, Robin Murphy wrote:
> >> On 17/12/15 22:31, Doug Anderson wrote:
> >>> On Thu, Dec 17, 2015 at 12:30 PM, Douglas Anderson wrote:
> The __iommu_alloc
Hi,
Both Andre and Diethard reported that the following kind of
SATA write IO errors on 32bit(ARM/i386) with PAE after the
commit 578270bfb(block: fix segment split):
[ 103.736982] ata1.00: exception Emask 0x0 SAct 0x30 SErr 0x0
action 0x6 frozen
[ 103.744476] ata1.00: failed command: WRITE
Andy Shevchenko writes:
> On Sun, Dec 20, 2015 at 10:17 PM, Andy Shevchenko
> wrote:
>> On Sun, Dec 20, 2015 at 8:49 PM, Måns Rullgård wrote:
>>> Julian Margetson writes:
On 12/20/2015 1:11 PM, Måns Rullgård wrote:
> Julian Margetson writes:
>>
[ 48.769671] ata3.00: failed com
Hi Tomasz,
On Friday 18 December 2015 15:05:45 Tomasz Figa wrote:
> On Fri, Dec 18, 2015 at 7:31 AM, Doug Anderson wrote:
> > On Thu, Dec 17, 2015 at 12:30 PM, Douglas Anderson wrote:
> >> The __iommu_alloc_buffer() is expected to be called to allocate pretty
> >> sizeable buffers. Upon simple te
Hi
> > +thermal: thermal@e61f {
> > + compatible ="renesas,thermal-r8a7790",
> > + "renesas,rcar-gen2-thermal",
> > + "renesas,rcar-thermal";
>
> Isn't having both mutually exclusive?
"rcar-thermal" is very basic version of "rcar-gen2",
and "rcar-ge
ec53500f "kvm: Add VFIO device" added a special KVM pseudo-device which is
used to handle any necessary interactions between KVM and VFIO.
Currently that device is built on x86 and ARM, but not powerpc, although
powerpc does support both KVM and VFIO. This makes things awkward in
userspace
Curre
Måns Rullgård writes:
> Andy Shevchenko writes:
>
>> On Sun, Dec 20, 2015 at 8:49 PM, Måns Rullgård wrote:
>>> Julian Margetson writes:
On 12/20/2015 1:11 PM, Måns Rullgård wrote:
> Julian Margetson writes:
>>
[ 48.769671] ata3.00: failed command: READ FPDMA QUEUED
>>>
>>> Wel
On Fri, Dec 18, 2015 at 12:35:47PM +1100, Alexey Kardashevskiy wrote:
> The vfio_iommu_spapr_tce_create struct has 4x32bit and 2x64bit fields
> which should have resulted in sizeof(fio_iommu_spapr_tce_create) equal
> to 32 bytes. However due to the gcc's default alignment, the actual
> size of this
Andy Shevchenko writes:
> On Sun, Dec 20, 2015 at 8:49 PM, Måns Rullgård wrote:
>> Julian Margetson writes:
>>> On 12/20/2015 1:11 PM, Måns Rullgård wrote:
Julian Margetson writes:
>
>>> [ 48.769671] ata3.00: failed command: READ FPDMA QUEUED
>>
>> Well, that didn't help. I still think
Andy Shevchenko writes:
> On Sun, Dec 20, 2015 at 8:49 PM, Måns Rullgård wrote:
>> Julian Margetson writes:
>>> On 12/20/2015 1:11 PM, Måns Rullgård wrote:
Julian Margetson writes:
>
>>> [ 48.769671] ata3.00: failed command: READ FPDMA QUEUED
>>
>> Well, that didn't help. I still think
Some architectures do not implement PTRACE_GETREGSET nor
PTRACE_SETREGSET (required by HAVE_ARCH_TRACEHOOK) but only implement
PTRACE_GETREGS and PTRACE_SETREGS (e.g. User-mode Linux).
This improve seccomp selftest portability for architectures without
HAVE_ARCH_TRACEHOOK support by defining a new
Add subarchitecture-independent implementation of asm-generic/syscall.h
allowing access to user system call parameters and results:
* syscall_get_nr()
* syscall_rollback()
* syscall_get_error()
* syscall_get_return_value()
* syscall_set_return_value()
* syscall_get_arguments()
* syscall_set_argumen
Hi Stephen,
On Thu, 10 Dec 2015 11:18:47 +1100 Stephen Rothwell
wrote:
>
> Hi Al,
>
> After merging the vfs tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> fs/orangefs/symlink.c:26:2: error: unknown field 'follow_link' specified in
> initializer
> .follow_link =
Things remain fairly normal. Last week rc5 was very small indeed, this
week we have a slightly bigger rc6. The main difference is that rc6
had a network pull in it.
But rc6 is still pretty small, and the patch looks pretty normal: just
over 60% drivers, 16% core networking, 13% architecture update
Am 21.12.2015 um 01:03 schrieb Mickaël Salaün:
> This fix two related bugs:
> * PTRACE_GETREGS doesn't get the right orig_ax (syscall) value
> * PTRACE_SETREGS can't set the orig_ax value (erased by initial value)
>
> Remove the now useless and error-prone get_syscall().
>
> Signed-off-by: Mickaë
This brings SECCOMP_MODE_STRICT and SECCOMP_MODE_FILTER support through
prctl(2) and seccomp(2) to User-mode Linux for i386 and x86_64
subarchitectures.
secure_computing() is called first in handle_syscall() so that the
syscall emulation will be aborted quickly if matching a seccomp rule.
This is
This fix two related bugs:
* PTRACE_GETREGS doesn't get the right orig_ax (syscall) value
* PTRACE_SETREGS can't set the orig_ax value (erased by initial value)
Remove the now useless and error-prone get_syscall().
Signed-off-by: Mickaël Salaün
Cc: Jeff Dike
Cc: Richard Weinberger
Cc: Thomas G
This series add seccomp support to User-mode Linux (i386 and x86_64
subarchitectures) and fix ptrace issues. This apply on v4.4-rc4 and pass all
the 48 tests from selftest/seccomp.
Regards,
Mickaël
Mickaël Salaün (4):
um: Fix ptrace GETREGS/SETREGS bugs
selftests/seccomp: Remove the need for
On 2015/12/20 18:47, Eric W. Biederman wrote:
> Dongsheng Yang writes:
>
>> On 12/20/2015 10:37 AM, Al Viro wrote:
>>> On Sun, Dec 20, 2015 at 10:14:29AM +0800, Dongsheng Yang wrote:
On 12/17/2015 07:23 PM, Dongsheng Yang wrote:
> Hi guys,
> We are working on making core dump b
On 2015-12-21 04:42, Kent Overstreet wrote:
On Mon, Dec 21, 2015 at 04:25:12AM +0500, Artem S. Tashkinov wrote:
On 2015-12-20 23:18, Christoph Hellwig wrote:
>On Sun, Dec 20, 2015 at 09:51:14AM -0800, Linus Torvalds wrote:
>>Kent, Jens, Christoph et al,
>> please see this bugzilla:
>>
>> https:
On Mon, Dec 21, 2015 at 04:25:12AM +0500, Artem S. Tashkinov wrote:
> On 2015-12-20 23:18, Christoph Hellwig wrote:
> >On Sun, Dec 20, 2015 at 09:51:14AM -0800, Linus Torvalds wrote:
> >>Kent, Jens, Christoph et al,
> >> please see this bugzilla:
> >>
> >> https://bugzilla.kernel.org/show_bug.cgi?
On 2015-12-20 23:44, Kent Overstreet wrote:
On Sun, Dec 20, 2015 at 07:18:01PM +0100, Christoph Hellwig wrote:
On Sun, Dec 20, 2015 at 09:51:14AM -0800, Linus Torvalds wrote:
> Kent, Jens, Christoph et al,
ie please see this bugzilla:
>o
> httpps://bugzilla.kernel.org/show_bug.cgi?id=109661
>
On 2015-12-20 23:41, Linus Torvalds wrote:
On Sun, Dec 20, 2015 at 10:18 AM, Christoph Hellwig wrote:
Artem,
can you re-check the commits around this series again? I would be
extremtly surprised if it's really this particular commit and not
one just before it causing the problem - it just all
Hi Mike,
Today's linux-next merge of the orangefs tree got a conflict in:
Makefile
between commit:
1ec218373b8e ("Linux 4.4-rc2")
from Linus' tree and commit:
575e946125f7 ("Orangefs: change pvfs2 filenames to orangefs")
from the orangefs tree.
You should really remove this EXTRAVERSI
1 - 100 of 274 matches
Mail list logo
