On Monday 28 November 2016 01:12 PM, Tomi Valkeinen wrote:
> On 28/11/16 07:24, Sekhar Nori wrote:
>> On Friday 25 November 2016 09:07 PM, Bartosz Golaszewski wrote:
>>> It has been determined that the maximum resolution supported correctly
>>> by tilcdc rev1 on da850 SoCs is 800x600@60. Due to mem
When a hardware issue happened as described by inline comments, the register
write pattern looks like the following:
+ wmb();
There might be a memory barrier between these two write operations, so add wmb
to ensure an flip from 0 to 1 for NCR.
Signed-off-by: Zumeng Chen
---
drivers/net
This is what is in the laptop:
01:00.0 Network controller [0280]: Broadcom Limited BCM43142 802.11b/g/n
[14e4:4365] (rev 01)
Subsystem: Dell Device [1028:0018]
Flags: bus master, fast devsel, latency 0, IRQ 18
Memory at b040 (64-bit, non-prefetchable) [size=32K]
MYIR Tech Limited offers a range of ARM powered development boards and SoMs,
for details reference a list on http://elinux.org/Development_Platforms#ARM
or company's website http://myirtech.com
Signed-off-by: Vladimir Zapolskiy
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 f
Thanks a lot, Alan,
I will send the v3 with your suggestion.
Best Regards
Jerry Huang
-Original Message-
From: Alan Stern [mailto:st...@rowland.harvard.edu]
Sent: Friday, November 25, 2016 11:14 PM
To: Jerry Huang
Cc: gre...@linuxfoundation.org; Ramneek Mehresh ;
julia.law...@lip6.fr;
Exception handlers which may run on IST stack calls ist_enter() at the
start of execution and ist_exit() in the end. The ist_enter() disables
preemption unconditionally and ist_exit() enables it.
Besides this, such exception handlers do additional unnecessary calls
of preempt_disable() and preempt
On Do, 2016-11-24 at 04:57 +0200, Michael S. Tsirkin wrote:
> sparse produces these warnings:
>
> drivers/gpu/drm/virtio/virtgpu_fb.c:340:27: warning: incorrect type in
> assignment (different address spaces)
> drivers/gpu/drm/virtio/virtgpu_fb.c:340:27:expected char [noderef]
> *screen_base
>
On Wed, Nov 23, 2016 at 01:45:16PM +0200, Alexander Shishkin wrote:
> Hi Greg,
>
> Let's try again. These are my updates for STM and Intel TH for
> v4.10. Please consider pulling. Thanks.
>
> The following changes since commit a25f0944ba9b1d8a6813fd6f1a86f1bd59ac25a6:
>
> Linux 4.9-rc5 (2016-1
On Fri, Nov 18, 2016 at 06:58:23PM +0530, Kishon Vijay Abraham I wrote:
> Hi Greg,
>
> Please find the pull request for 4.10 merge window below. Major changes
> include adding anew phy driver for meson8b/gxbb SoC, removing a couple
> of phy drivers from unsupported SoCs, adding sysfs entry to perf
On Tue, Nov 22, 2016 at 03:08:03PM +0900, Chanwoo Choi wrote:
> Dear Greg,
>
> This is extcon-next pull request for v4.10. I add detailed description of
> this pull request on below. Please pull extcon with following updates.
>
> Best Regards,
> Chanwoo Choi
>
> The following changes since commi
On 28/11/16 07:24, Sekhar Nori wrote:
> On Friday 25 November 2016 09:07 PM, Bartosz Golaszewski wrote:
>> It has been determined that the maximum resolution supported correctly
>> by tilcdc rev1 on da850 SoCs is 800x600@60. Due to memory throughput
>> constraints we must filter out higher modes.
>
On 2016/11/27 1:17, Alexei Starovoitov wrote:
On Sat, Nov 26, 2016 at 07:03:34AM +, Wang Nan wrote:
Add basic clang support in clang.cpp and test__clang() testcase. The
first testcase checks if builtin clang is able to generate LLVM IR.
tests/clang.c is a proxy. Real testcase resides in
u
On 28 November 2016 at 15:21, Greg KH wrote:
> On Mon, Nov 28, 2016 at 02:29:25PM +0800, Baolin Wang wrote:
>> Hi Mathias,
>>
>> On 24 November 2016 at 19:16, Baolin Wang wrote:
>> > Since these 'return' statements are not generally useful in void
>> > function, remove them. Also remove one unuse
On Mon, Nov 07, 2016 at 03:25:01PM +0900, Joonsoo Kim wrote:
> On Fri, Oct 14, 2016 at 12:03:10PM +0900, js1...@gmail.com wrote:
> > From: Joonsoo Kim
> >
> > Hello,
> >
> > Changes from v5
> > o Add acked/reviewed-by tag from Vlastimil and Aneesh
> > o Rebase on next-20161013
> > o Cosmetic cha
On Sat 26-11-16 08:42:40, Li Zefan wrote:
> On 2016/11/25 17:46, Arnd Bergmann wrote:
> > On Friday, November 25, 2016 1:46:04 PM CET Zefan Li wrote:
> >> On 2016/11/25 12:55, Kirtika Ruchandani wrote:
> >>> 'struct cpuset* cs' that is set but not used, was introduced in commit
> >>> 1f7dd3e5a6e4 (
On Fri, Nov 11, 2016 at 02:30:39AM -0800, David Rientjes wrote:
> On Fri, 11 Nov 2016, Joonsoo Kim wrote:
>
> > Hello, David.
> >
> > Maintaining acitve/free_slab counters looks so complex. And, I think
> > that we don't need to maintain these counters for faster slabinfo.
> > Key point is to rem
+Sai for Xilinx perspective.
On 25.11.2016 16:24, Sebastian Frias wrote:
> Hi,
>
> When using the Arasan SDHCI HW IP, there is a set of parameters called
> "Hardware initialized registers"
>
> (Table 7, Section "Pin Signals", page 56 of Arasan "SD3.0/SDIO3.0/eMMC4.4
> AHB Host Controller", revis
On Sun, Nov 27, 2016 at 04:59:14PM -0700, Jonathan Corbet wrote:
> On Fri, 25 Nov 2016 22:58:14 +0100
> Peter Zijlstra wrote:
>
> > Not a fan of this. The atomic_ops.txt file needs a lot of love, and I
> > wouldn't want to edit a .rst file.
> >
> > Then again, I probably won't actually get aroun
Stephen Rothwell writes:
> Hi all,
>
> After merging the wireless-drivers-next tree, today's linux-next build
> (x86_64 allmodconfig) produced this warning:
>
> In file included from include/linux/usb/ch9.h:35:0,
> from include/linux/usb.h:5,
> from
> drivers/ne
Commit-ID: adee8705d2517f0e163ffc45e8d7f9e97a58f1f6
Gitweb: http://git.kernel.org/tip/adee8705d2517f0e163ffc45e8d7f9e97a58f1f6
Author: Peter Foley
AuthorDate: Sat, 26 Nov 2016 17:22:29 -0500
Committer: Ingo Molnar
CommitDate: Mon, 28 Nov 2016 07:47:22 +0100
x86/build: Annotate die() wi
Commit-ID: 9190e21780dfeff524a67c6e7b806c8a9d496086
Gitweb: http://git.kernel.org/tip/9190e21780dfeff524a67c6e7b806c8a9d496086
Author: Paul Bolle
AuthorDate: Fri, 25 Nov 2016 13:41:47 +0100
Committer: Ingo Molnar
CommitDate: Mon, 28 Nov 2016 07:49:17 +0100
x86/build: Remove three unnee
Commit-ID: 55f856e640560494518eaf24fe9d2d2089fba71a
Gitweb: http://git.kernel.org/tip/55f856e640560494518eaf24fe9d2d2089fba71a
Author: Josh Poimboeuf
AuthorDate: Sun, 27 Nov 2016 23:13:07 -0600
Committer: Ingo Molnar
CommitDate: Mon, 28 Nov 2016 07:47:54 +0100
x86/unwind: Fix guess-unw
Commit-ID: 20ab6677716c7bbdcfd1cdb9aef296a0b3101f73
Gitweb: http://git.kernel.org/tip/20ab6677716c7bbdcfd1cdb9aef296a0b3101f73
Author: Borislav Petkov
AuthorDate: Sat, 26 Nov 2016 15:27:06 +0100
Committer: Ingo Molnar
CommitDate: Mon, 28 Nov 2016 07:46:03 +0100
x86/platform/olpc: Fix r
Marc, could you try this patch please? I think it should be pretty clear
it should help you but running it through your use case would be more
than welcome before I ask Greg to take this to the 4.8 stable tree.
Thanks!
On Wed 23-11-16 07:34:10, Michal Hocko wrote:
[...]
> commit b2ccdcb731b666aa2
Commit-ID: 06cbbac0f57d947656a12c30a0a69d4cf0ac6dea
Gitweb: http://git.kernel.org/tip/06cbbac0f57d947656a12c30a0a69d4cf0ac6dea
Author: Paul Bolle
AuthorDate: Fri, 25 Nov 2016 13:38:34 +0100
Committer: Ingo Molnar
CommitDate: Mon, 28 Nov 2016 07:49:17 +0100
x86/build: Don't use $(LINUXI
Commit-ID: 6248f4567442081994ad61c63bd9870e147983e0
Gitweb: http://git.kernel.org/tip/6248f4567442081994ad61c63bd9870e147983e0
Author: Borislav Petkov
AuthorDate: Fri, 25 Nov 2016 12:14:48 +0100
Committer: Ingo Molnar
CommitDate: Mon, 28 Nov 2016 07:45:17 +0100
x86/boot/64: Optimize fi
On Mon, Nov 28, 2016 at 02:29:25PM +0800, Baolin Wang wrote:
> Hi Mathias,
>
> On 24 November 2016 at 19:16, Baolin Wang wrote:
> > Since these 'return' statements are not generally useful in void
> > function, remove them. Also remove one unuseful 'break' statement
> > in xhci_setup_addressable_
On 25 November 2016 at 21:00, Mark Brown wrote:
> On Tue, Nov 22, 2016 at 09:40:07AM +1100, NeilBrown wrote:
>
>> I agree that the question of where the responsibility for information
>> aggregation lies is open for discussion. If fact all details on how
>> things should work are always open for d
On 28/11/16 03:55 PM, Daniel Vetter wrote:
> On Sat, Nov 26, 2016 at 7:22 PM, David Herrmann wrote:
>> On Sat, Nov 26, 2016 at 7:07 PM, Dmitry Vyukov wrote:
>>> grep "card0" dmesg:
>>> [5.298617] device: 'card0': device_add
>>> [5.298946] PM: Adding info for No Bus:card0
>>> [6.436178
28.11.2016 04:29, David Miller пишет:
> From: Nikita Yushchenko
> Date: Fri, 25 Nov 2016 13:02:00 +0300
>
>> +int i, ret;
>> +
>> +ret = pm_runtime_get_sync(&fep->pdev->dev);
>> +if (IS_ERR_VALUE(ret)) {
>> +memset(data, 0, sizeof(*data) * ARRAY_SIZE(fec_stats));
>> +
vxlan_fdb_append may return error, so add the proper check,
otherwise it will cause memory leak.
Signed-off-by: Haishuang Yan
---
drivers/net/vxlan.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/drivers/net/vxlan.c b/drivers/net/vxlan.c
index 21e92be..3b7b237 10
Dear Sir/s,
Please see attached.
Thanks and regards,
Accounts Department
Al Omraniya Trading Co. LLC
P.O. Box: 10757, Al Khabaisi Area,
Deira 2, Dubai, U.A.E.
Tel: +971 4 268 2730 / Fax: +971 4 268 4117
> From: Stephen Hemminger [mailto:step...@networkplumber.org]
> Sent: Sunday, November 27, 2016 01:06
> To: Vitaly Kuznetsov
> Cc: de...@linuxdriverproject.org; linux-kernel@vger.kernel.org; KY Srinivasan
> ; Haiyang Zhang ; Dexuan Cui
>
> Subject: Re: [PATCH 0/7] hv: CPU onlining/offlining fixes
Current Linux has of_clk_get(), but doesn't have devm_of_clk_get().
This patch adds it. This is based on devm_clk_get()
Signed-off-by: Kuninori Morimoto
---
v1 -> v2
- update git log
drivers/clk/clkdev.c | 26 ++
include/linux/clk.h | 7 +++
2 files changed, 33 i
On Sat, Nov 26, 2016 at 7:22 PM, David Herrmann wrote:
> On Sat, Nov 26, 2016 at 7:07 PM, Dmitry Vyukov wrote:
>> grep "card0" dmesg:
>> [5.298617] device: 'card0': device_add
>> [5.298946] PM: Adding info for No Bus:card0
>> [6.436178] device: 'card0': device_add
>> [6.436488] PM
Dear Sir/s,
Please see attached.
Thanks and regards,
Accounts Department
Al Omraniya Trading Co. LLC
P.O. Box: 10757, Al Khabaisi Area,
Deira 2, Dubai, U.A.E.
Tel: +971 4 268 2730 / Fax: +971 4 268 4117
On Sat, Nov 26, 2016 at 04:00:46AM -0800, Paul E. McKenney wrote:
> On Fri, Nov 25, 2016 at 12:34:26AM -0800, Paul E. McKenney wrote:
> > On Tue, Nov 22, 2016 at 05:12:20PM +0900, Byungchul Park wrote:
> > > On Wed, Nov 09, 2016 at 03:32:15PM +0900, Byungchul Park wrote:
> > > > Currently rcu code
_dsa_register_switch() gets a dsa_switch_tree object either via
dsa_get_dst() or via dsa_add_dst(). Former path does not increase kref
in returned object (resulting into caller not owning a reference),
while later path does create a new object (resulting into caller owning
a reference).
The rest o
For some mobile devices with strict power management, we also want to suspend
the host when the slave is detached for power saving. Thus we add the host
suspend/resume functions to support this requirement.
Signed-off-by: Baolin Wang
---
Changes since v3:
- No updates.
Changes since v2:
- Remo
Fix reversed conditional checking if HOSTCC is clang.
Suppress warnings about unsupported optimization options.
Suppress warnings about unused functions, as they are generated for
every module and are therefore far too spammy.
Disable clang's integrated assembler which is incompatible with kernel
a
Enable the xhci plat runtime PM for parent device to suspend/resume xhci.
Also call pm_runtime_get_noresume() in probe() function in case the parent
device doesn't call suspend/resume callback by runtime PM now.
Signed-off-by: Baolin Wang
---
Changes since v3:
- Fix kbuild error.
Changes since
On 2016/11/27 1:29, Alexei Starovoitov wrote:
On Sat, Nov 26, 2016 at 07:03:44AM +, Wang Nan wrote:
PerfModule::doJIT JIT compile perfhook functions and saves result into
a map. Add a test case for it.
At this stage perfhook functions can do no useful things because they
can't invoke exte
Hi Boris, Stefan,
> On Tue, 22 Nov 2016 13:04:11 -0800
> Stefan Agner wrote:
>
> > On 2016-11-01 00:10, Lukasz Majewski wrote:
> > > From: Sascha Hauer
> > >
> > > The use of the ipg clock was introduced with commit 7b27c160c681
> > > ("pwm: i.MX: fix clock lookup").
> > > In the commit messag
> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
> Sent: Friday, November 25, 2016 20:49
> To: de...@linuxdriverproject.org
> Cc: linux-kernel@vger.kernel.org; KY Srinivasan ; Haiyang
> Zhang ; Dexuan Cui ;
> Stephen Hemminger
> Subject: [PATCH 1/7] hv: acquire vmbus_connection.channel_mutex
On 2016/11/27 1:25, Alexei Starovoitov wrote:
On Sat, Nov 26, 2016 at 07:03:38AM +, Wang Nan wrote:
getBPFObjectFromModule() is introduced to compile LLVM IR(Module)
to BPF object. Add new testcase for it.
Test result:
$ ./buildperf/perf test -v clang
51: Test builtin clang support
Hi Mathias,
On 24 November 2016 at 19:16, Baolin Wang wrote:
> Since these 'return' statements are not generally useful in void
> function, remove them. Also remove one unuseful 'break' statement
> in xhci_setup_addressable_virt_dev() function.
>
> Signed-off-by: Baolin Wang
> ---
> Changes sinc
Dear Concern,
I am Talent Scout For BLUE SKY FILM STUDIO, Present Blue sky Studio a
Film Corporation Located in the United State, is Soliciting for the
Right to use Your Photo/Face and Personality as One of the Semi -Major
Role/ Character in our Upcoming ANIMATED Stereoscope 3D Movie-The Story
of
On Wed, Nov 23, 2016 at 9:03 PM, Sekhar Nori wrote:
> On Thursday 24 November 2016 04:18 AM, David Lechner wrote:
>> On 11/23/2016 04:32 PM, Kevin Hilman wrote:
>>> David Lechner writes:
>>>
On 11/23/2016 04:27 AM, Bartosz Golaszewski wrote:
> 2016-11-22 23:23 GMT+01:00 David Lechner :
>
On Mon, Nov 28, 2016 at 7:40 AM, Coly Li wrote:
> On 2016/11/28 上午12:32, Konstantin Khlebnikov wrote:
>> Current implementation employ 16bit counter of active stripes in lower
>> bits of bio->bi_phys_segments. If request is big enough to overflow
>> this counter bio will be completed and freed too
Hi all,
Changes since 20161125:
New tree: modules
The mmc tree gained a conflict against the block tree.
The edac-amd tree gained a conflict agaainst the edac tree.
The kvm tree gained a conflict against the tip tree.
The akpm-current tree still had its build failure for which I added a
suppl
Dear Stefan, Boris,
> On 2016-11-23 00:38, Boris Brezillon wrote:
> > On Tue, 22 Nov 2016 13:55:33 -0800
> > Stefan Agner wrote:
> >
> >> On 2016-11-01 00:10, Lukasz Majewski wrote:
> >> > This commit provides apply() callback implementation for i.MX's
> >> > PWMv2.
> >> >
> >> > Suggested-by: S
On Sun, Nov 27, 2016 at 9:26 PM, Haishuang Yan
wrote:
> It shold reserved sizeof(ipv6hdr) for geneve in ipv6 tunnel.
>
> Fixes: c3ef5aa5e5 ('geneve: Merge ipv4 and ipv6 geneve_build_skb()')
>
> Signed-off-by: Haishuang Yan
Thanks for fix.
Acked-by: Pravin B Shelar
+Qiang, who is working on it.
On 2016年11月27日 22:07, Christian König wrote:
Am 27.11.2016 um 15:02 schrieb Haggai Eran:
On 11/25/2016 9:32 PM, Jason Gunthorpe wrote:
On Fri, Nov 25, 2016 at 02:22:17PM +0100, Christian König wrote:
Like you say below we have to handle short lived in the usual w
>
> From: Michael S. Tsirkin [mailto:m...@redhat.com]
> Sent: Monday, November 28, 2016 1:09 PM
> To: Gonglei (Arei)
> Subject: Re: [virtio-dev] Re: [PATCH v2 2/2] crypto: add virtio-crypto driver
>
> On Mon, Nov 28, 2016 at 04:47:21AM +, Gonglei (Arei) wrote:
> > Michael, I'd like to add vi
Hello,
On (11/28/16 09:41), Minchan Kim wrote:
>
> I'm going on a long vacation so forgive if I respond slowly. :)
no prob. have a good one!
> On Sun, Nov 27, 2016 at 10:19:10PM +0900, Sergey Senozhatsky wrote:
[..]
> > wondering - how many pages can it hold? we are in low memory, that's why w
On Thursday 24 November 2016 03:01 PM, Bartosz Golaszewski wrote:
> Currently the memory controller and master priorities drivers are
> enabled in da850.dtsi. For boards for which there are no settings
> defined, this makes these drivers emit error messages.
>
> Disable the nodes in da850.dtsi and
It shold reserved sizeof(ipv6hdr) for geneve in ipv6 tunnel.
Fixes: c3ef5aa5e5 ('geneve: Merge ipv4 and ipv6 geneve_build_skb()')
Signed-off-by: Haishuang Yan
---
drivers/net/geneve.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/geneve.c b/drivers/net/geneve.c
On Thursday 24 November 2016 08:05 PM, Fabien Parent wrote:
> In order to avoid Linux generating a random mac address on every boot,
> add an ethernet0 alias that will allow u-boot to patch the dtb with
> the MAC address programmed into the EEPROM.
>
> Signed-off-by: Fabien Parent
Applied to v4.
Congratulations,
Dear Mr. /Mrs. you are lucky to have been chosen in the BMW 2016 lottery draw.
That was just concluded in an E lottery online machine draw and the email with
lotto number BMW216021653096 and ticket draw number 5000342. Has won
$150,000(ONE HUNDRED AND FIFTHY THOUSAND DOLLARS)
VE
On Friday 25 November 2016 09:07 PM, Bartosz Golaszewski wrote:
> It has been determined that the maximum resolution supported correctly
> by tilcdc rev1 on da850 SoCs is 800x600@60. Due to memory throughput
> constraints we must filter out higher modes.
>
> Specify the max-bandwidth property for
On 27-11-16, 00:13, Sebastian Andrzej Siewior wrote:
> Install the callbacks via the state machine.
>
> Cc: "Rafael J. Wysocki"
> Cc: Viresh Kumar
> Cc: linux...@vger.kernel.org
> Signed-off-by: Sebastian Andrzej Siewior
> ---
> drivers/cpufreq/acpi-cpufreq.c | 93
> --
My attempt at fixing some KASAN false positive warnings was rather brain
dead, and it broke the guess unwinder. With frame pointers disabled,
/proc//stack is broken:
# cat /proc/1/stack
[] 0x
Restore the code flow to more closely resemble its previous state, while
still using
Hi Jessica,
On Sat, 26 Nov 2016 14:42:09 -0800 Jessica Yu wrote:
>
> Could you please add the modules-next branch at:
>
>git://git.kernel.org/pub/scm/linux/kernel/git/jeyu/linux.git modules-next
>
> to linux-next? The branch contains patches for modules targeted for the next
> merge window.
On Mon, Nov 28, 2016 at 04:47:21AM +, Gonglei (Arei) wrote:
> Michael, I'd like to add virtio-crypto stuff to your maintaining part likes
> the virtio-net/blk parts so that the corresponding patches
> can be CC'ed to you too because the virtio-crypto doesn't lay in
> driver/virtio directory. W
On 11/26/2016 04:20 AM, Lino Sanfilippo wrote:
> Add driver for Alacritech gigabit ethernet cards with SLIC (session-layer
> interface control) technology. The driver provides basic support without
> SLIC for the following devices:
>
> - Mojave cards (single port PCI Gigabit) both copper and fiber
From: Timur Tabi
Date: Sun, 27 Nov 2016 20:11:17 -0600
> David Miller wrote:
>> Series applied, thanks.
>
> I was really hoping you'd give me the chance to test the patches
> before applying them.
Sorry, if anything is broken I will happily revert if it isn't
fixed promptly.
Hi Aniroop,
On Fri, Nov 25, 2016 at 12:54:39AM +0530, Aniroop Mathur wrote:
> msleep(1~20) may not do what the caller intends, and will often sleep longer.
> (~20 ms actual sleep for any value given in the 1~20ms range)
> This is not the desired behaviour for many cases like device resume time,
>
Hi Michael,
>
> Subject: [virtio-dev] Re: [PATCH v2 2/2] crypto: add virtio-crypto driver
>
> On Tue, Nov 22, 2016 at 04:10:23PM +0800, Gonglei wrote:
> > This patch introduces virtio-crypto driver for Linux Kernel.
> >
> > The virtio crypto device is a virtual cryptography device
> > as well as
On 2016/11/28 上午12:32, Konstantin Khlebnikov wrote:
> Current implementation employ 16bit counter of active stripes in lower
> bits of bio->bi_phys_segments. If request is big enough to overflow
> this counter bio will be completed and freed too early.
>
> Fortunately this not happens in default c
On 11/24/2016 12:17 AM, Sascha Hauer wrote:
> On Wed, Nov 23, 2016 at 10:57:13AM -0800, Florian Fainelli wrote:
>> On 11/23/2016 02:01 AM, Sascha Hauer wrote:
>>> With this patch the serial core provides LED triggers for RX and TX.
>>>
>>> As the serial core layer does not know when the hardware
Hi Kuninori,
[auto build test ERROR on robh/for-next]
[also build test ERROR on v4.9-rc7]
[cannot apply to glikely/devicetree/next asoc/for-next next-20161125]
[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/l
Thanks a lot for you look into this patch, I will fixed these typos.
Best Regards
Jerry Huang
-Original Message-
From: Sergei Shtylyov [mailto:sergei.shtyl...@cogentembedded.com]
Sent: Friday, November 25, 2016 9:12 PM
To: Jerry Huang ; st...@rowland.harvard.edu;
gre...@linuxfoundati
skip_emulated_instruction is going to grow a return value, and we'll need
to return it from kvm_emulate_cpuid.
Signed-off-by: Kyle Huey
---
arch/x86/include/asm/kvm_host.h | 2 +-
arch/x86/kvm/cpuid.c| 3 ++-
arch/x86/kvm/svm.c | 3 +--
arch/x86/kvm/vmx.c |
We can't return both the pass/fail boolean for the vmcs and the upcoming
continue/exit-to-userspace boolean for skip_emulated_instruction out of
nested_vmx_check_vmcs, so move skip_emulated_instruction out of it instead.
Additionally, VMENTER/VMRESUME only trigger singlestep exceptions when
they a
Similar to the code in kvm_vcpu_check_singlestep, check for TF and,
depending on the origin, synthesize a DB exception or an exit to userspace.
Signed-off-by: Kyle Huey
---
arch/x86/kvm/vmx.c | 21 +
1 file changed, 21 insertions(+)
diff --git a/arch/x86/kvm/vmx.c b/arch/x86
Return 1 (for the moment) from skip_emulated_instruction and propagate it
through. This is straightforward, except for:
- ICEBP, which is already inside a trap, so avoid triggering another trap.
- Instructions that can trigger exits to userspace, such as the IO insns,
MOVs to CR8, and HALT. If s
The functions being moved ahead of skip_emulated_instruction here don't
need updated IPs, and moving skip_emulated_instruction to the end will
make it easier to return its return value.
Signed-off-by: Kyle Huey
---
arch/x86/kvm/vmx.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletion
Hi Kuninori,
[auto build test ERROR on robh/for-next]
[also build test ERROR on v4.9-rc7]
[cannot apply to glikely/devicetree/next asoc/for-next next-20161125]
[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/l
KVM does not currently honor the trap flag when emulating instructions that
cause VM exits. This is observable from guest userspace, try stepping on a
CPUID instruction in gdb in a KVM guest. The program will stop two
instructions after CPUID.
To fix this, in skip_emulated_instruction we can check
On 25-11-16, 17:50, Arnd Bergmann wrote:
> The addition of the generic governor support marked the
> intel_pstate_exit_perf_limits as inline, which fixed a warning,
> but it introduced another warning:
>
> drivers/cpufreq/intel_pstate.c: In function ‘intel_pstate_exit_perf_limits’:
> drivers/cpufr
Hi
> [auto build test ERROR on robh/for-next]
> [also build test ERROR on v4.9-rc7]
> [cannot apply to glikely/devicetree/next asoc/for-next next-20161125]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improve the system]
>
> url:
> https://github.com/0d
Originally pfn_pte(pfn, prot) macro had this definition:
__pte(((pfn) << PAGE_SHIFT) | pgprot_val(prot))
The value of pfn (Page Frame Number) is shifted to the left to get the
value of pte (Page Table Entry). Usually a 4-byte value is passed to
this macro as value of pfn. However if Linux is
GPIO7 is configured in POWERHOLD mode which has higher priority
over DEV_ON bit and keeps the PMIC supplies on even after the DEV_ON
bit is turned off. This property enables driver to over ride the
POWERHOLD value to GPIO7 so as to turn off the PMIC in power off
scenarios.
Signed-off-by: Keerthy
Hi all,
Today's linux-next merge of the kvm tree got a conflict in:
arch/x86/kvm/cpuid.c
between commit:
c592b5734706 ("x86/fpu: Remove use_eager_fpu()")
from the tip tree and commit:
4504b5c9414c ("kvm: x86: Add AVX512_4VNNIW and AVX512_4FMAPS support")
from the kvm tree.
I fixed it
On Thursday 24 November 2016 02:15 PM, Lee Jones wrote:
On Thu, 24 Nov 2016, Keerthy wrote:
On Tuesday 15 November 2016 07:13 AM, Rob Herring wrote:
On Thu, Nov 10, 2016 at 10:39:16AM +0530, Keerthy wrote:
GPIO7 is configured in POWERHOLD mode which has higher priority
over DEV_ON bit and
Hi Borislav,
Today's linux-next merge of the edac-amd tree got a conflict in:
drivers/edac/edac_mc.c
between commit:
ef91afa61088 ("edac: move documentation from edac_mc.c to edac_core.h")
from the edac tree and commit:
c73e8833bec5 ("EDAC, mc: Fix locking around mc_devices list")
from
Hi Kuninori,
[auto build test ERROR on robh/for-next]
[also build test ERROR on v4.9-rc7]
[cannot apply to glikely/devicetree/next asoc/for-next next-20161125]
[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/l
On 11/27/2016 06:10 PM, John Muir wrote:
On 2016.11.27, at 15:00 , Guenter Roeck wrote:
On Sat, Nov 26, 2016 at 09:15:37PM -0800, John Muir wrote:
Move the tmp108 driver from hwmon attribute groups to
hwmon_chip_info.
Signed-off-by: John Muir
---
Hi John,
please have a look at the followi
Hi Guys,
When I run stress-ng via the following steps on one ARM64 dual
socket system(Cavium Thunder), the kernel oops[1] can often be
triggered after running the stress test for several hours(sometimes
it may take longer):
- git clone git://kernel.ubuntu.com/cking/stress-ng.git
- apply the attac
Add do_arch_prctl_common() to handle arch_prctls that are not specific to 64
bit mode. Call it from the syscall entry point, but not any of the other
callsites in the kernel, which all want one of the existing 64 bit only
arch_prctls.
Signed-off-by: Kyle Huey
---
arch/x86/include/asm/proto.h | 3
Hook up arch_prctl to call do_arch_prctl() on x86-32, and in 32 bit compat
mode on x86-64. This allows us to have arch_prctls that are not specific to
64 bits.
On UML, simply stub out this syscall.
Signed-off-by: Kyle Huey
---
arch/x86/entry/syscalls/syscall_32.tbl | 1 +
arch/x86/kernel/proces
Intel supports faulting on the CPUID instruction beginning with Ivy Bridge.
When enabled, the processor will fault on attempts to execute the CPUID
instruction with CPL>0. This will allow a ptracer to emulate the CPUID
instruction.
Bit 31 of MSR_PLATFORM_INFO advertises support for this feature. I
On 2016/11/28 上午10:50, Peter Foley wrote:
> Fixes below error with clang:
> ../drivers/md/bcache/sysfs.c:759:3: error: function definition is not allowed
> here
> { return *((uint16_t *) r) - *((uint16_t *) l); }
> ^
> ../drivers/md/bcache/sysfs.c:789:32: erro
Test disabling and reenabling the cpuid instruction via the new arch_prctl
ARCH_SET_CPUID, retrieving the current state via ARCH_GET_CPUID, and the
expected behaviors across fork() and exec().
Signed-off-by: Kyle Huey
---
tools/testing/selftests/x86/Makefile | 2 +-
tools/testing/selftest
In order to introduce new arch_prctls that are not 64 bit only, rename the
existing 64 bit implementation to do_arch_prctl_64(). Also rename the second
argument to arch_prctl(), which will no longer always be an address.
Signed-off-by: Kyle Huey
Reviewed-by: Andy Lutomirski
---
arch/um/include/
Hardware support for faulting on the cpuid instruction is not required to
emulate it, because cpuid triggers a VM exit anyways. KVM handles the relevant
MSRs (MSR_PLATFORM_INFO and MSR_MISC_FEATURES_ENABLE) and upon a
cpuid-induced VM exit checks the cpuid faulting state and the CPL.
kvm_require_cp
Use the SYSCALL_DEFINE2 macro instead of manually defining it.
Signed-off-by: Kyle Huey
---
arch/x86/kernel/process_64.c | 3 ++-
arch/x86/um/syscalls_64.c| 3 ++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kernel/process_64.c b/arch/x86/kernel/process_64.c
index
Intel supports faulting on the CPUID instruction beginning with Ivy Bridge.
When enabled, the processor will fault on attempts to execute the CPUID
instruction with CPL>0. Exposing this feature to userspace will allow a
ptracer to trap and emulate the CPUID instruction.
When supported, this featur
rr (http://rr-project.org/), a userspace record-and-replay reverse-
execution debugger, would like to trap and emulate the CPUID instruction.
This would allow us to a) mask away certain hardware features that rr does
not support (e.g. RDRAND) and b) enable trace portability across machines
by provi
On Sun, Nov 27, 2016 at 07:34:17PM +0800, Cao jin wrote:
> It is user space driver's or device-specific driver's(in guest) responsbility
> to do a serious recovery when error happened. Link-reset is one part of
> recovery, when pci device is assigned to VM via vfio, link-reset will do
> twice in ho
1 - 100 of 286 matches
Mail list logo
