On 1/15/21 2:24 AM, Zhang Han wrote:
> Fix problems about spaces:
> -operator needs spaces around it, add them.
> -somespaces are redundant, remove them.
>
> Signed-off-by: Zhang Han
> ---
> audio/audio_template.h | 2 +-
> audio/coreaudio.c | 2 +-
> audio/dsoundaudio.c| 2 +-
> audio/
On Thu, Jan 14, 2021 at 01:24:37PM -0500, Jag Raman wrote:
>
>
> > On Jan 14, 2021, at 1:00 PM, Daniel P. Berrangé wrote:
> >
> > On Thu, Jan 14, 2021 at 12:55:58PM -0500, Jag Raman wrote:
> >>
> >>
> >>> On Jan 14, 2021, at 11:27 AM, Stefan Hajnoczi wrote:
> >>>
> >>> On Thu, Jan 14, 2021
Igor Mammedov writes:
> On Thu, 7 Jan 2021 16:14:49 +0100
> Vitaly Kuznetsov wrote:
>
>> Enabling Hyper-V emulation for a Windows VM is a tiring experience as it
>> requires listing all currently supported enlightenments ("hv-*" CPU
>> features) explicitly. We do have 'hv-passthrough' mode enab
14.01.2021 20:02, Max Reitz wrote:
There are a couple of environment variables that we fetch with
os.environ.get() without supplying a default. Clearly they are required
and expected to be set by the ./check script (as evidenced by
execute_setup_common(), which checks for test_dir and
qemu_defau
On 1/15/21 4:27 AM, zhenwei pi wrote:
> According to NVMe spec 1.4 section
"According to NVMe spec 1.4 section 5.14.1.2"
> , introduce bit 5
> for "Persistent Memory Region has become read-only or unreliable".
>
> Signed-off-by: zhenwei pi
> ---
> include/block/nvme.h | 1 +
> 1 file changed,
On 1/15/21 4:27 AM, zhenwei pi wrote:
> During smart critical warning injection by setting property from QMP
> command, also try to trigger asynchronous event.
>
> Suggested by Keith, if a event has already been raised, there is no
> need to enqueue the duplicate event any more.
>
> Signed-off-by
On 1/15/21 8:56 AM, Gan Qixin wrote:
> The pwm_qom_get function didn't free "response", which caused an indirect
> memory leak. So use qobject_unref() to fix it.
>
> ASAN shows memory leak stack:
>
> Indirect leak of 7416 byte(s) in 18000 object(s) allocated from:
> #0 0x7f96e2f79d4e in _
> -Original Message-
> From: Lukas Straub
> Sent: Thursday, January 14, 2021 9:51 PM
> To: Zhang, Chen
> Cc: Jason Wang ; qemu-dev de...@nongnu.org>; Eric Blake ; Dr. David Alan
> Gilbert ; Markus Armbruster ;
> Zhang Chen
> Subject: Re: [PATCH 3/3] net/colo-compare: Add handler for
Depending on the client activity, the server can be asked to open a huge
number of file descriptors and eventually hit RLIMIT_NOFILE. This is
currently mitigated using a reclaim logic : the server closes the file
descriptors of idle fids, based on the assumption that it will be able
to re-open them
> -Original Message-
> From: Lukas Straub
> Sent: Thursday, January 14, 2021 9:45 PM
> To: Zhang, Chen
> Cc: Jason Wang ; qemu-dev de...@nongnu.org>; Eric Blake ; Dr. David Alan
> Gilbert ; Markus Armbruster ;
> Zhang Chen
> Subject: Re: [PATCH 3/3] net/colo-compare: Add handler for
The following changes since commit 7c79721606be11b5bc556449e5bcbc331ef6867d:
Merge remote-tracking branch 'remotes/rth-gitlab/tags/pull-tcg-20210113' into
staging (2021-01-14 09:54:29 +)
are available in the Git repository at:
https://gitlab.com/gkurz/qemu.git tags/9p-next-2021-01-15
f
Hi,
> These patches were made in response to Volkers patches which dealt with
> cleaning up my previous code:
> https://www.mail-archive.com/qemu-devel@nongnu.org/msg766686.html
> and thus are meant to be merged after Volker's patches.
>
> Hopefully, this commit message isn't too daunting ;)
Volker Rümelin writes:
> Currently there is a crackling noise with SDL2 audio playback.
> Commit bcf19777df: "audio/sdlaudio: Allow audio playback with
> SDL2" already mentioned the crackling noise.
>
> Add an out.buffer-count option to give users a chance to select
> sane settings for glitch fre
On Wed, Jan 13, 2021 at 05:22:56PM +0100, Greg Kurz wrote:
> Hi Bharata,
>
> On Wed, 6 Jan 2021 14:29:10 +0530
> Bharata B Rao wrote:
>
> > If KVM_CAP_RPT_INVALIDATE KVM capability is enabled, then
> >
> > - indicate the availability of H_RPT_INVALIDATE hcall to the guest via
> > ibm,hyperta
On Thu, 14 Jan 2021 at 23:17, Alex Bennée wrote:
>
> Shreyansh Chouhan writes:
>
> > Just an update:
> >
> > I've studied the virtio specification along with the source code and I
> now
> > understand what the device implementation is
> > going to look like. Also I understand the source code a l
401 - 415 of 415 matches
Mail list logo