On 15/04/25 2:56 pm, Daniel P. Berrangé wrote:
!---|
CAUTION: External Email
|---!
On Tue, Apr 15, 2025 at 02:50:39PM +0530, Manish wrote:
On 14/04/25 7:56 pm
On 14/04/25 7:56 pm, Fabiano Rosas wrote:
!---|
CAUTION: External Email
|---!
Manish Mishra writes:
We allocate extra metadata SKBs in case of a zerocopy send
ENOBUF error with a zerocopy sendmsg,
we flush the error queue and retry once more.
Signed-off-by: Manish Mishra
---
include/io/channel-socket.h | 5 +++
io/channel-socket.c | 74 ++---
2 files changed, 65 insertions(+), 14 deletions(-)
V2:
1. Removed
On 21/03/25 9:15 pm, Daniel P. Berrangé wrote:
!---|
CAUTION: External Email
|---!
On Sun, Mar 16, 2025 at 09:52:31PM -0400, Manish Mishra wrote:
We allocate
Hi Daniel, Peter,
Please let me know if this latest patch looks good?
On 17/03/25 7:22 am, Manish Mishra wrote:
We allocate extra metadata SKBs in case of a zerocopy send. This metadata
memory is accounted for in the OPTMEM limit. If there is any error while
sending zerocopy packets or if
dirty_sync_missed_zero_copy migration stat again.
Signed-off-by: Manish Mishra
---
include/io/channel-socket.h | 5 +++
io/channel-socket.c | 74 ++---
2 files changed, 65 insertions(+), 14 deletions(-)
diff --git a/include/io/channel-socket.h b/include/io/channel-socket.h
Sure
Thanks
Manish Mishra
On 11/03/25 8:52 pm, Peter Xu wrote:
!---|
CAUTION: External Email
|---!
On Tue, Mar 11, 2025 at 04:15:38AM +0530, Manish wrote
Thanks Peter, Daniel
Are there any code pointers where something similar is done? I can
follow that.
Thanks
Manish Mishra
On 11/03/25 1:33 am, Peter Xu wrote:
!---|
CAUTION: External Email
dirty_sync_missed_zero_copy migration stat.
2. Made the call to qio_channel_socket_flush_internal() from
qio_channel_socket_writev() non-blocking.
Signed-off-by: Manish Mishra
---
include/io/channel.h | 3 +-
io/channel-socket.c| 57 --
migration/migration
On 27/02/25 11:26 pm, Peter Xu wrote:
!---|
CAUTION: External Email
|---!
On Thu, Feb 27, 2025 at 10:30:31PM +0530, Manish wrote:
Again really sorry, missed
|---!
On Fri, Feb 21, 2025 at 04:44:48AM -0500, Manish Mishra wrote:
We allocate extra metadata SKBs in case of zerocopy send. This metadata memory
is accounted for in the OPTMEM limit. If there is any error with sending
zerocopy data or if zerocopy was
:
!---|
CAUTION: External Email
|---!
On Fri, Feb 21, 2025 at 04:44:48AM -0500, Manish Mishra wrote:
We allocate extra metadata SKBs in case of zerocopy send. This metadata memory
is
requests fail to
allocate any new SKB, leading to an ENOBUF error.
To workaround this, if we encounter an ENOBUF error with a zerocopy sendmsg,
we flush the error queue and retry once more.
Signed-off-by: Manish Mishra
---
include/io/channel-socket.h | 1 +
io/channel-socket.c | 52
On 01/08/24 8:41 pm, Xiaoyao Li wrote:
!---|
CAUTION: External Email
|---!
On 8/1/2024 6:25 PM, Igor Mammedov wrote:
On Thu, 1 Aug 2024 15:36:10 +0530
Manish
and it doesn't affect anything.
Yes, that makes sense, I will send a updated patch by tomorrow if no one
has any objection with this.
regards
john
Thanks
Manish Mishra
On 30/07/24 6:39 pm, Igor Mammedov wrote:
!---|
CAUTION: External Email
|---!
On Mon, 29 Jul 2024 19:42:39 +0700
Manish wrote:
On 29/07/24 7:18 pm, Igor
24, 2024 at 03:59:29PM +0530, Manish wrote:
Leaf 0x1f is superset of 0xb, so it makes sense to set 0x1f equivalent
to 0xb by default and workaround windows issue.>
This change adds a
new property 'cpuid-0x1f-enforce' to set leaf 0x1f equivalent to 0xb in
case extended CPU to
Hi Igor, Anything further on this?
Thanks
Manish Mishra
On 24/07/24 8:30 pm, Zhao Liu wrote:
!---|
CAUTION: External Email
|---!
Hi Igor,
On Wed, Jul 24, 2024
:59:29PM +0530, Manish wrote:
Leaf 0x1f is superset of 0xb, so it makes sense to set 0x1f equivalent
to 0xb by default and workaround windows issue.>
This change adds a
new property 'cpuid-0x1f-enforce' to set leaf 0x1f equivalent to 0xb in
case extended CPU topology is not configured
On 24/07/24 4:43 pm, John Levon wrote:
On Wed, Jul 24, 2024 at 03:59:29PM +0530, Manish wrote:
Leaf 0x1f is superset of 0xb, so it makes sense to set 0x1f equivalent
to 0xb by default and workaround windows issue.>
This change adds a
new property 'cpuid-0x1f-enforce' to
|---!
(+Xiaoyao, whose TDX work may also be related with this.)
Hi Manish,
Thanks for your patch! Some comments below.
On Mon, Jul 22, 2024 at 10:18:59AM +, manish.mishra wrote:
Date: Mon, 22 Jul 2024 10:18:59 +
From
Thanks Zhao, Igor and Xiaoyao, I have sent v1 for this
https://patchwork.ozlabs.org/project/qemu-devel/patch/20240724075226.212882-1-manish.mis...@nutanix.com/.
On 23/07/24 8:33 pm, Igor Mammedov wrote:
!---|
CAUTION: External
Thanks for response Zhao.
On 19/07/24 3:20 pm, Manish Mishra wrote:
!---|
CAUTION: External Email
|---!
Hi Manish,
(+Paolo and Daniel)
On Thu, Jul 18, 2024 at 11:44
all zeros. This seems to work
fine. Our understanding is that current QEMU behaviour is not incorrect but
still does the above mentioned workaround makes sense? And if we look it is the
same as bare-metal so it should not be unreasonable. If so will be happy to
send a patch for same.
Thanks
Manish Mishra
Thanks Wang Lie. Yes sure will do same until we have new version.
Thanks
Manish Mishra
From: Wang, Lei
Date: Tuesday, 23 April 2024 at 12:50 PM
To: Manish Mishra , qemu-devel@nongnu.org
Cc: christopher.r.blev...@intel.com ,
robert...@linux.intel.com
Subject: Re: Missing features in QEMU
/7eb061b06e97af9a8da7f31b839d78997ae737fc.
There may be other features too missing but we were particularly interested in
these three. So just wanted to understand if there is any reason for this. Any
help on this will be really appreciated. 😊
Thanks
Manish Mishra
On Thu, Mar 7, 2019 at 9:55 PM Marc-André Lureau
wrote:
>
> Hi
>
> On Thu, Mar 7, 2019 at 3:00 PM manish jaggi wrote:
> >
> > Hi List,
> > I am trying to run qemu with spice gl=on with the below command line
> > and getting errors.
> >
> > qemu-s
e_dma_buf_export not supported error ?
What I could be missing here
Need help/guidance.
-Thanks
Manish
CCing a larger audience.
Please review.
On 10/23/2018 03:51 PM, Jaggi, Manish wrote:
> From: Manish Jaggi
>
> This patch introduces an error code KVM_EINVARIANT which is returned
> by KVM when userland tries to set an invariant register.
>
> The need for this error code is i
> On 05-Sep-2018, at 6:11 PM, Jaggi, Manish wrote:
>
>
>
>> On 05-Sep-2018, at 5:50 PM, Andrew Jones wrote:
>>
>> External Email
>>
>> On Wed, Sep 05, 2018 at 11:46:11AM +, Jaggi, Manish wrote:
>>> (a) Changes in KVM:
>>>
> On 05-Sep-2018, at 5:50 PM, Andrew Jones wrote:
>
> External Email
>
> On Wed, Sep 05, 2018 at 11:46:11AM +, Jaggi, Manish wrote:
>> (a) Changes in KVM:
>>
>> - Introducing a specific error code (KVM_EINVARIANT) in case of invariant
>> writes.
&g
> On 04-Sep-2018, at 3:24 PM, Andrew Jones wrote:
>
> External Email
>
> On Tue, Sep 04, 2018 at 09:16:58AM +, Jaggi, Manish wrote:
>>> On 31-Aug-2018, at 4:41 PM, Andrew Jones wrote:
>>> I think the sequence should look something like this:
>>
> On 31-Aug-2018, at 4:41 PM, Andrew Jones wrote:
>
> External Email
>
> Manish,
>
> Your mail reader doesn't appear to be providing any quoting, so I'm not
> sure I found all your replies. I've tried to fix up the quoting in order
> to reply here, b
On 29-Aug-2018, at 6:46 PM, Andrew Jones
mailto:drjo...@redhat.com>> wrote:
External Email
On Wed, Aug 29, 2018 at 12:40:08PM +, Jaggi, Manish wrote:
On 28-Aug-2018, at 10:57 PM, Dr. David Alan Gilbert
mailto:dgilb...@redhat.com>> wrote:
External Email
(Cc'ing i
> On 28-Aug-2018, at 10:57 PM, Dr. David Alan Gilbert
> wrote:
>
> External Email
>
> (Cc'ing in Eric, Drew, and Peter for ARM stuff)
>
Thanks,
> * Jaggi, Manish (manish.ja...@cavium.com) wrote:
>>
>>
>>> On 23-Aug-2018, at 7:59
> On 23-Aug-2018, at 7:59 PM, Juan Quintela wrote:
>
> External Email
>
> "Jaggi, Manish" wrote:
>> Hi,
>
> Hi
>
> [Note that I was confused about what do you mean with problems with
> processorID. There is no processorID on the migration
dest_processor_id, so the qemu running
on destination machine will not complain. The overhead with this approach is
that the destination machines Id need to be known beforehand.
If there is some better way… please suggest.
Thanks,
Manish
the following devices needs to be emulated
1. CPU model (Cortex-A8)
2. RAM
3. UART
What other least number of devices needs to be emulated to for this
machine model to work well ?
Thanks,
Manish
t; -serial tcp::,server,
With the above command I have attached gdb with qemu.
Now I am not sure what needs to be done on host side(I have cross compiled
GDB in the Host file system).
Please help me what i need to do in host side ?
Thanks & Regards
Manish Tiwari
file with syntax similar to vmware
vmx file or bochs.
I have played with qemu code to do some experiments with config file. let me
know what you think.
---
regards
Manish Regmi
http://manish-cs.blogspot.com
Hi,
We are faceing one Problem in Qemu guest os winxp . The Qemu hbas been
installed in Linux CentOs 4.4 . Guest os detected the Realtek Lan Adapter .
BUt with is Adpeter we are unable get the IP from Our Dhcp Server. Could
you suggest how to do this.
Regards
Manish
On 12/6/06, Miroslav
41 matches
Mail list logo
