On 1/18/24 20:07, Igor Mammedov wrote:
On Thu, 18 Jan 2024 14:48:50 +0800
Kai wrote:
On 1/18/24 01:31, Peter Maydell wrote:
(cc'd the people listed for this file in MAINTAINERS)
On Tue, 9 Jan 2024 at 13:53, Kai Kang wrote:
When this section of source codes were added via c
On 1/18/24 01:31, Peter Maydell wrote:
(cc'd the people listed for this file in MAINTAINERS)
On Tue, 9 Jan 2024 at 13:53, Kai Kang wrote:
When this section of source codes were added via commit:
* 02e2da45c4 Add common BusState
it added devices to bus with LIST_INSERT_HEAD() which ope
On 1/9/24 17:52, kai.k...@windriver.com wrote:
From: Kai Kang
When this section of source codes were added via commit:
* 02e2da45c4 Add common BusState
it added devices to bus with LIST_INSERT_HEAD() which operated on the
single direction list. It didn't have something like LIST_INSERT
n the command
line.
Signed-off-by: Kai Kang
---
hw/core/qdev.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/core/qdev.c b/hw/core/qdev.c
index 43d863b0c5..5e2ff43715 100644
--- a/hw/core/qdev.c
+++ b/hw/core/qdev.c
@@ -89,7 +89,7 @@ static void bus_add_child(BusState
alls the realize function serial_isa_realizefn() with indexes "0"
and "1". But calls serial_isa_build_aml() with 1 and 0.
I didn't figure out the root cause. Which part of source codes should I
focus on next please?
Or fortunately someone just knows the root cause.
Thanks a lot.
--
Kai Kang
Wind River Linux
tence's second half, and looks it's better to
also call out "wrong XFRM value in SGX CPUID leaf" in the patch title.
Anyway ...
>
> Fixes: 301e90675c3f ("target/i386: Enable support for XSAVES based features")
>
> Signed-off-by: Yang Zhong
&g
On Mon, 2023-01-23 at 15:03 +0100, Vlastimil Babka wrote:
> On 12/22/22 01:37, Huang, Kai wrote:
> > > > I argue that this page pinning (or page migration prevention) is not
> > > > tied to where the page comes from, instead related to how the page will
> >
On Thu, 2022-12-22 at 18:15 +, Sean Christopherson wrote:
> On Wed, Dec 21, 2022, Chao Peng wrote:
> > On Tue, Dec 20, 2022 at 08:33:05AM +, Huang, Kai wrote:
> > > On Tue, 2022-12-20 at 15:22 +0800, Chao Peng wrote:
> > > > On Mon, Dec 19, 2022 at 08:4
On Wed, 2022-12-21 at 21:39 +0800, Chao Peng wrote:
> > On Tue, Dec 20, 2022 at 08:33:05AM +, Huang, Kai wrote:
> > > > On Tue, 2022-12-20 at 15:22 +0800, Chao Peng wrote:
> > > > > > On Mon, Dec 19, 2022 at 08:48:10AM +, Huang, Kai wrote:
> > >
On Tue, 2022-12-20 at 15:22 +0800, Chao Peng wrote:
> On Mon, Dec 19, 2022 at 08:48:10AM +, Huang, Kai wrote:
> > On Mon, 2022-12-19 at 15:53 +0800, Chao Peng wrote:
> > > >
> > > > [...]
> > > >
> > > > > +
> > > > &g
On Mon, 2022-12-19 at 15:53 +0800, Chao Peng wrote:
> >
> > [...]
> >
> > > +
> > > + /*
> > > + * These pages are currently unmovable so don't place them into
> > > movable
> > > + * pageblocks (e.g. CMA and ZONE_MOVABLE).
> > > + */
> > > + mapping = memfd->f_mapping;
> > > + mapping_set_une
On Fri, 2022-12-02 at 14:13 +0800, Chao Peng wrote:
>
> - /* flags is currently not used. */
> + /* 'flags' is currently not used. */
> if (attrs->flags)
> return -EINVAL;
Unintended code change.
>
> memfd_restricted() itself is implemented as a shim layer on top of real
> memory file systems (currently tmpfs). Pages in restrictedmem are marked
> as unmovable and unevictable, this is required for current confidential
> usage. But in future this might be changed.
>
>
I didn't dig full his
guest.
Link:
https://lore.kernel.org/lkml/166760360549.4906.809756297092548496.tip-bot2@tip-bot2/
Link:
https://lore.kernel.org/lkml/166760360934.4906.2427175408052308969.tip-bot2@tip-bot2/
Reviewed-by: Yang Zhong
Signed-off-by: Kai Huang
---
target/i386/cpu.c | 4 ++--
1 file changed, 2
On Thu, 2022-10-13 at 02:23 -0400, Yang Zhong wrote:
> > > enclave only supported SSE and x87 feature(xfrm=0x3).
> >
> > Is this true? Perhaps I am missing something, but it seems env-
> > > features[FEAT_XSAVE_XCR0_LO] only includes LBR bit, which is bit 15.
>
> We printed the XFRM value from
cx &= env->features[FEAT_XSAVE_XSS_LO];
> -*edx &= env->features[FEAT_XSAVE_XSS_HI];
> +*ecx &= env->features[FEAT_XSAVE_XCR0_LO];
> +*edx &= env->features[FEAT_XSAVE_XCR0_HI];
>
> /* FP and SSE are always allowed regardless of XSAVE/XCR0. */
> *ecx |= XSTATE_FP_MASK | XSTATE_SSE_MASK;
The code looks good:
Reviewed-by: Kai Huang
On Fri, 2021-04-30 at 14:24 +0800, Yang Zhong wrote:
> From: Sean Christopherson
>
> KVM_CAP_SGX_ATTRIBUTE is a proposed capability for Intel SGX that can be
> used by userspace to enable privileged attributes, e.g. access to the
> PROVISIONKEY.
>
> Signed-off-by: Sean Christopherson
> Signed-o
On Mon, 2021-04-19 at 18:01 +0800, Yang Zhong wrote:
> From: Sean Christopherson
>
> KVM_CAP_SGX_ATTRIBUTE is a proposed capability for Intel SGX that can be
> used by userspace to enable privileged attributes, e.g. access to the
> PROVISIONKEY.
>
> Signed-off-by: Sean Christopherson
> Signed-o
> > > future?
> > [Robert Hoo]
> > Thanks Eduardo for efforts in resolving this issue, introduced from my
> > Icelake CPU
> > model patch.
> > I've no idea about PCONFIG's detail and plan. Let me sync with Huang, Kai
> > and answer
>
ion
> is, "why enumerate WBNOINVD if its implementation is exactly the same
> as WBINVD?"
>
> WBNOINVD appears to be only partially documented in Intel document
> 319433-037, "Intel® Architecture Instruction Set Extensions and Future
> Features Programming Reference." In particular, there is no
> documentation regarding the instruction's behavior in VMX non-root
> mode. Does WBNOINVD cause a VM-exit when the VM-execution control,
> "WBINVD exiting," is set? If so, does it have the same VM-exit reason
> as WBINVD (54), or a different one? If it does have the same VM-exit
> reason (a la SVM), how does one distinguish a WBINVD VM-exit from a
> WBNOINVD VM-exit? If one can't distinguish (a la SVM), then it would
> seem that the VMX implementation also implements WBNOINVD as WBINVD.
> If that's the case, the question for VMX is the same as for SVM.
Unfortunately WBNOINVD interaction with VMX has not been made to public yet. I
am reaching out internally to see when it can be done. I agree it may not be
necessary to expose WBNOINVD if its implementation is exactly the same as
WBINVD, but it also doesn't have any harm, right?
Thanks,
-Kai
Hi!
I've googled: "usb" "designware" "otg" "datasheet"
I think this is the kernel driver for this device:
https://github.com/torvalds/linux/tree/master/drivers/usb/dwc3
Maybe it should be possible to use this as a reference? Maybe try to
redirect the proprietary drivers system calls? I don't kno
Public bug reported:
I build lib32-qemu which is a multilib variant for mips o32 on project
Yocto with qemumips64. It finally runs command and fails:
mips-wrsmllib32-linux-gcc -meb -mabi=32 -mhard-float -fstack-protector-strong
-Wformat -Wformat-security -Werror=format-security
--sysroot=/m
Thanks!
Thanks,
-Kai
On 3/14/2017 5:57 AM, Paolo Bonzini wrote:
On 13/03/2017 15:58, fangying wrote:
Hi, Huang Kai
After weeks of intensive testing, we think the problem is solved and
this issue can be closed.
Thanks for the update. We got to the same conclusion.
Paolo
test going?
Thanks,
-Kai
It works well on my side with the patch. Thanks!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1658634
Title:
Can't get correct display with latest QEMU and OVMF BIOS
Status in QEMU:
Confirmed
s not clear.
Thanks,
Kai
On Mon, Jan 23, 2017 at 4:50 AM, Laszlo Ersek (Red Hat)
wrote:
> (1) What phase of the guest do you get invalid video output in? Do you
> see the TianoCore splash screen? Does the grub2 menu appear?
>
> (2) I cannot reproduce the issue (with a different gu
Public bug reported:
I tried to install a Ubuntu 16.04.1 Desktop 64bits with latest QEMU and OVMF
UEFI BIOS, however I can't get correct display output with default vga
configuration (-vga std). However, qemu works with a couple of different
configurations:
1. "-vga cirrus" + "-bios OVMF.fd": w
Public bug reported:
Looking for the 'continue'/'resume' option I found this order that was not
quite 'alphabetical'.
It had me overlook the 'cont' option at glance. Which is just a little
impractical.
...
boot_set bootdevice -- define new values for the boot device list
change device filename
Public bug reported:
When using the '-display' option the parameter 'none' is not the only
string that causes the behaviour of 'none'. I can use '-display
noneMICKEYMOUSE' and still have the none behaviour.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bu
Hello Chris,
Steps taken to test the proposed package:
1) enabled trusty-proposed
2) installed qemu-system-arm qemu-system-common qemu-system-misc
qemu-system-x86 qemu-user version 2.0.0+dfsg-2ubuntu1.25
3) again on a second trusty14.04 server
4) migrate 41 running VM's (uptimes vary between 1 a
We have four identical Ubuntu servers running libvirt/kvm/qemu, with
access to CEPH rbd filesystems. Guests can be live migrated between
them. However, live migration leads in ~30% of the cases to guests being
stuck at 100%. Only a few times we had the patience to wait, and upon
logging in our pass
I can reasonably assume that this solved my problem. I've live migrated
41 VM's 5 times between 2 hypervisors without the 100% cpu problem
appearing.
My production servers run 2.0.0+dfsg-2ubuntu1.22, and still observe the
same problem.
Attached is the patch that I created with quilt in debian/pa
That patch does not apply cleanly on qemu (2.0.0+dfsg, from trusty).
There are changes in "kvmclock_pre_save" and "kvmclock_post_save",
there's only "kvmclock_vm_state_change" in 2.0.0.
Peeking at the 4 referenced patches on
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=786789
the code change
@serge,
I'd be happy to test each of the patches, but considering the length of
this page I'd like an exact link to a patch and/or patches that need to
be tested, and against which version (trusty-security i suppose?).
--
You received this bug notification because you are a member of qemu-
devel
On 6/8/2016 6:46 AM, Alex Williamson wrote:
On Tue, 7 Jun 2016 17:21:06 +1200
"Huang, Kai" wrote:
On 6/7/2016 3:58 PM, Alex Williamson wrote:
On Tue, 7 Jun 2016 11:20:32 +0800
Peter Xu wrote:
On Mon, Jun 06, 2016 at 11:02:11AM -0600, Alex Williamson wrote:
On Mon, 6 Jun 201
t only works on intel IOMMU.
And what do you mean asynchronous invalidations? I think the iova of the
changed mappings cannot be used until the mappings are invalidated. It
doesn't matter whether the invalidation is done via QI or register.
Thanks,
-Kai
C: Page-walk Coherency
This
Hi Guangrong,
How about also add SGX to Skylake?
Thanks,
-Kai
On 4/27/2016 8:13 PM, Xiao Guangrong wrote:
From: Eduardo Habkost
Introduce Skylake-Client cpu mode which inherits the features from
Broadwell and supports some additional features that are: MPX,
XSAVEC, XSAVES and XGETBV1
Note
Those auxiliary repositories referenced by git-submodule, such as dtc.git
in my last email, are only available on git.qemu.org.
Regards,
Kai
野田 開
2015-12-10 0:24 GMT+08:00 Laszlo Ersek :
> On 12/09/15 17:09, Kai Noda wrote:
> > Hello, is it possible to enable Git-over-HTTP on git
/dtc.git/
">here.
Apache/2.2.14 (Ubuntu) Server at git.qemu.org Port 80
I'd like to access to QEMU Git repositories through HTTP proxy which blocks
the Git port 9418/TCP.
Best regards,
Kai
野田 開
No time to debug, invaliding...
** Changed in: qemu (Ubuntu)
Status: Incomplete => Invalid
** Information type changed from Public to Private
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/151
ProcCmdline: qemu-system-x86_64 -machine ubuntu,accel=kvm -m 1024
-device virtio-vga -cdrom ubuntu-15.10-desktop-amd64.iso
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1516203
Title:
qemu-system-x
Public bug reported:
Starting a VM like so:
/usr/bin/qemu-system-x86_64 -machine accel=kvm -monitor
unix:/srv/localfs/Samsung_SSD_840_PRO_Series_S1AXNSAF320206J/vg-virt/lv-
gentoosummerschool/gentoo-summerschool/gentoo-
summerschool.img.monitor,server,nowait -name gentoo-summerschool
-chardev
soc
On Sun, Jan 19, 2014 at 10:11 PM, Alex Williamson
wrote:
> On Sun, 2014-01-19 at 22:03 +0800, Kai Huang wrote:
>> On Sat, Jan 18, 2014 at 3:25 AM, Alex Williamson
>> wrote:
>> > From: Alexey Kardashevskiy
>> >
>> > VFIO virtualizes MSIX table for the gu
s. Does MSIX have one
dedicated bar when qemu emulating the device? Looks your code maps
both the content before and after the MSIX table? If MSIX has
dedicated bar, I think we can just skip the MSIX bar, why do we need
to map the context before and after the MSIX table?
Thanks,
-Kai
> si
On 05/17/2012 01:43 PM, Paolo Bonzini wrote:
Il 17/05/2012 19:53, Kai Meyer ha scritto:
Morally it's wrong, but a copyright holder cannot stop you on
moral grounds. Legally, you should consult a lawyer.
What you say is morally wrong here is a bit ambiguous to me. Do you
mean using mod
ionality to your customers, keep clear from legal
grey areas, contribute to QEMU positively, and perhaps get some
advertising for your product.
Paolo
I think just plain iSCSI is a more appropriate solution for our needs,
as interesting as this sounds :).
Again, thanks for the clarity on these issu
On 05/16/2012 11:48 AM, Paolo Bonzini wrote:
Il 16/05/2012 19:06, Kai Meyer ha scritto:
1) It's been suggested to me that since we have the rights to distribute
our closed source shared library, there is a precedence for being able
to distributed a modified version of qemu that does run
On 03/01/2012 11:54 PM, Paolo Bonzini wrote:
It does not matter whether it is upstream or not.
When you distribute your modified QEMU binary, anyone who receives it
has the right to ask you for the complete corresponding source code.
I also suggest that you write a wrapper around your library
On 05/16/2012 12:21 PM, Anthony Liguori wrote:
On 05/16/2012 12:48 PM, Paolo Bonzini wrote:
Il 16/05/2012 19:06, Kai Meyer ha scritto:
1) It's been suggested to me that since we have the rights to
distribute
our closed source shared library, there is a precedence for being able
to distri
From: "NODA, Kai"
GHashTableIter was first introduced in glib 2.16.
This patch removes it in favor of older g_hash_table_find()
for better compatibility with RHEL5.
Signed-off-by: NODA, Kai
---
Added sign-off. Sorry for inconvenience!
qapi/qmp-input-visito
From: "NODA, Kai"
GHashTableIter was first introduced in glib 2.16.
This patch removes it in favor of older g_hash_table_find()
for better compatibility with RHEL5.
---
qapi/qmp-input-visitor.c | 25 +
1 file changed, 17 insertions(+), 8 deletions(-)
diff --
Hi Paolo,
I've encountered the same problem as Erik on my RHEL5 machine with
glib 2.12, and made a patch to replace GHashTableIter with
g_hash_table_find().
https://github.com/nodakai/QEMU/commit/4a9dd009feb1d78e3566069336a0d1b9a296bd23
I think it's an almost same approach with yours, but have not
From: Paolo Bonzini [pbonz...@redhat.com]
Sent: Thursday, March 01, 2012 11:54 PM
To: Kai Meyer
Cc: Anthony Liguori; Stefan Weil; qemu-devel@nongnu.org; Nate Bushman
Subject: Re: Add support for new image type
Il 01/03/2012 22:14, Kai Meyer ha scritto
On 03/01/2012 02:05 PM, Anthony Liguori wrote:
On 03/01/2012 02:18 PM, Stefan Weil wrote:
Am 01.03.2012 21:10, schrieb Stefan Weil:
Am 01.03.2012 20:45, schrieb Kai Meyer:
On 03/01/2012 08:03 AM, Kevin Wolf wrote:
Am 29.02.2012 22:52, schrieb Kai Meyer:
Is it possible to extend qemu to
On 03/01/2012 01:18 PM, Stefan Weil wrote:
Am 01.03.2012 21:10, schrieb Stefan Weil:
Am 01.03.2012 20:45, schrieb Kai Meyer:
On 03/01/2012 08:03 AM, Kevin Wolf wrote:
Am 29.02.2012 22:52, schrieb Kai Meyer:
Is it possible to extend qemu to support a new image type? I have an
image type that
On 03/01/2012 01:10 PM, Stefan Weil wrote:
Am 01.03.2012 20:45, schrieb Kai Meyer:
On 03/01/2012 08:03 AM, Kevin Wolf wrote:
Am 29.02.2012 22:52, schrieb Kai Meyer:
Is it possible to extend qemu to support a new image type? I have an
image type that is ready for consumption and I'm lo
On 03/01/2012 08:03 AM, Kevin Wolf wrote:
Am 29.02.2012 22:52, schrieb Kai Meyer:
Is it possible to extend qemu to support a new image type? I have an
image type that is ready for consumption and I'm looking for the
integration point between qemu and the new image format.
Which image form
Is it possible to extend qemu to support a new image type? I have an
image type that is ready for consumption and I'm looking for the
integration point between qemu and the new image format.
-Kai Meyer
On 12/20/2011 06:02 PM, Hui Kai Ran wrote:
On 12/19/2011 09:11 PM, Corey Bryant wrote:
The most common use of -net tap is to connect a tap device to a
bridge. This
requires the use of a script and running qemu as root in order to
allocate a
tap device to pass to the script.
This model is
On 12/19/2011 09:11 PM, Corey Bryant wrote:
The most common use of -net tap is to connect a tap device to a bridge. This
requires the use of a script and running qemu as root in order to allocate a
tap device to pass to the script.
This model is great for portability and flexibility but it's in
On 12/15/2011 04:18 PM, Stefan Hajnoczi wrote:
On Thu, Dec 15, 2011 at 02:00:11PM +0800, Hui Kai Ran wrote:
but for virtio blk device , how can i open multifunction ability?
Please search the mailing list archives, Anthony has posted instructions
in previous threads.
Stefan
I found it
Hi,
It seems that qemu now have the ability to install pci device with
mutlifunction=on, such as
I got a cfg file to start qemu
[device "ehci"]
driver = "ich9-usb-ehci1"
addr = "0d.7"
multifunction = "on"
[device "ehci1"]
driver = "ich9-usb-ehci1"
addr = "0d.3"
multifunction = "on
2011/10/24 Bob Breuer :
> Kai Tietz wrote:
>> Hi,
>>
>> For trunk-version I have a tentative patch for this issue. On 4.6.x
>> and older branches this doesn't work, as here we can't differenciate
>> that easy between ms- and sysv-abi.
>>
>>
ceptions over VC generated code. So I
would strongly recomment to use the slower, but more reliable SjLj
throwing mechanism on Windows 32-bit.
Regards,
Kai
Hi,
For trunk-version I have a tentative patch for this issue. On 4.6.x
and older branches this doesn't work, as here we can't differenciate
that easy between ms- and sysv-abi.
But could somebody give this patch a try?
Regards,
Kai
ChangeLog
* config/i
05 AM, Bob Breuer wrote:
>> Kai Tietz wrote:
>>> 2011/10/18 Bob Breuer :
>>>> Kai Tietz wrote:
>>>>> 2011/10/17 Bob Breuer :
>>>>>> Richard Henderson wrote:
>>>>>>> On 10/17/2011 07:09 AM, Bob Breuer wrote:
>>>&g
2011/10/18 Bob Breuer :
> Kai Tietz wrote:
>> 2011/10/17 Bob Breuer :
>>> Richard Henderson wrote:
>>>> On 10/17/2011 07:09 AM, Bob Breuer wrote:
>>>>> I don't think this is a free/g_free issue. If I use the following
>>>>> patch,
urn i;
> }
>
> int main(void)
> {
> return test();
> }
>
> Remove the asm statement to make it not crash. Obviously with
> omit-frame-pointer, gcc can shove anything into ebp.
>
> Bob
This crash isn'r related to ebp existing, or not. The issue is the
hidden argu
68 matches
Mail list logo
