interrupt controller) to handle both wired interrupts and MSIs
- There's no user-visible change here, but only a developer-visible
change: in terms of what's being emulated in userspace vs. in-kernel
irqchip.)
So, if it's still not too late:
Tested-by: Kashyap C
On Mon, Feb 17, 2025 at 04:17:20PM +0800, Yong-Xuan Wang wrote:
> This series introduces the user-space AIA MSI emulation when using KVM
> acceleration.
>
> After this series, RISC-V QEMU virt machine with KVM acceleration has
> 3 parameters to control the type of irqchip and its emulation method:
On Tue, Feb 18, 2025 at 11:34:38AM +, Peter Maydell wrote:
> On Tue, 18 Feb 2025 at 11:29, Kashyap Chamarthy wrote:
[...]
> > > Maybe we shall
> > > - rename KVM vCPU Features -> KVM only vCPU Features
> > > - Add a TCG only vCPU features including both SME
(Cc: Richard Henderson; context: "SME" and "RME" feature discussion
below.)
On Mon, Feb 17, 2025 at 06:43:01PM +0100, Eric Auger wrote:
> Hi Kashyap,
Hey,
>
> On 2/17/25 5:37 PM, Kashyap Chamarthy wrote:
[...]
> > Signed-off-by: Kashyap Chamarthy
>
On Mon, Feb 17, 2025 at 01:23:51PM +, Peter Maydell wrote:
> On Thu, 13 Feb 2025 at 08:44, Kashyap Chamarthy wrote:
> >
> > In v2:
> >
> > - Add live-migration context to the PAuth docs (Marc Zyngier)
> >
> > - Fix the Arm capitlalization
Signed-off-by: Kashyap Chamarthy
---
docs/system/arm/cpu-features.rst | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/docs/system/arm/cpu-features.rst b/docs/system/arm/cpu-features.rst
index 37d5dfd15b..a596316384 100644
--- a/docs/system/arm/cpu
rchive/html/qemu-devel/2025-01/msg05137.html
- docs/cpu-features: Update "PAuth" (Pointer Authentication) details
[2] 6fe6d6c9a9 (docs: Be consistent about capitalization of 'Arm',
2020-03-09)
Signed-off-by: Kashyap Chamarthy
---
docs/devel/testing/qgraph.rst
long with `pauth`, a couple of properties can be
controlled -- they're are related to cryptographic algorithm choice.
Thanks to Peter Maydell and Marc Zyngier for explaining more about PAuth
on IRC (#qemu, OFTC).
Signed-off-by: Kashyap Chamarthy
---
v2: address Marc Zyngier's comme
inconsistency - there's a KVM-only CPU features
section, but no TCG-only section. I thought when there are more
TCG-only CPU features, that section can be added back in. Or I can add
that back in, if anyone feels strongly about it.
Kashyap Chamarthy (3):
docs/cpu-features: Consistently
On Thu, Feb 13, 2025 at 09:09:12PM +, Alex Bennée wrote:
> Kashyap Chamarthy writes:
>
> > Signed-off-by: Kashyap Chamarthy
>
> Should we add vCPU to glossary.rst?
Ah, I didn't notice this in the tree. I can add as a follow-up later.
PS: I sent the patch while o
long with `pauth`, a couple of properties can be
controlled -- they're are related to cryptographic algorithm choice.
Thanks to Peter Maydell and Marc Zyngier for explaining more about PAuth
on IRC (#qemu, OFTC).
Signed-off-by: Kashyap Chamarthy
---
v2: address Marc Zyngier's comme
Signed-off-by: Kashyap Chamarthy
---
docs/system/arm/cpu-features.rst | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/docs/system/arm/cpu-features.rst b/docs/system/arm/cpu-features.rst
index 37d5dfd15b..a596316384 100644
--- a/docs/system/arm/cpu
ere are more
TCG-only CPU features, that section can be added back in. Or I can add
that back in, if anyone feels strongly about it.
Kashyap Chamarthy (3):
docs/cpu-features: Consistently use vCPU instead of VCPU
docs/cpu-features: Update "PAuth" (Pointer Authentication) details
thought when there are more
TCG-only CPU features, that section can be added back in. Or I can add
that back in, if anyone feels strongly about it.
Kashyap Chamarthy (3):
docs/cpu-features: Consistently use vCPU instead of VCPU
docs/cpu-features: Update "PAuth" (Pointer Authenticati
On Mon, Jan 27, 2025 at 01:06:44PM +, Peter Maydell wrote:
> On Mon, 20 Jan 2025 at 09:06, Kashyap Chamarthy wrote:
> >
> > On Sat, Jan 18, 2025 at 10:04:37AM +, Marc Zyngier wrote:
> > > On Fri, 17 Jan 2025 19:11:06 +,
> > > Kashyap Chamarth
On Sat, Jan 18, 2025 at 10:04:37AM +, Marc Zyngier wrote:
> On Fri, 17 Jan 2025 19:11:06 +,
> Kashyap Chamarthy wrote:
> >
> > PAuth (Pointer Authentication), a security feature in software, is
> > relevant for both KVM and QEMU. Relect this fact into the do
-only CPU features
section, but no TCG-only section. I thought when there are more
TCG-only CPU features, that section can be added back in. Or I can add
that back in, if anyone feels strongly about it.
Kashyap Chamarthy (2):
docs/cpu-features: Consistently use vCPU instead of VCPU
docs/cpu-fe
Signed-off-by: Kashyap Chamarthy
---
docs/system/arm/cpu-features.rst | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/docs/system/arm/cpu-features.rst b/docs/system/arm/cpu-features.rst
index a5fb929243c..78f18c87a81 100644
--- a/docs/system/arm/cpu
long with `pauth`, a couple of properties can be
controlled -- they're are related to cryptographic algorithm choice.
Thanks to Peter Maydell and Marc Zyngier for explaining more about PAuth
on IRC (#qemu, OFTC).
Signed-off-by: Kashyap Chamarthy
---
docs/system/arm/cpu-features.rst | 23 +
, 110 deletions(-)
Looks good to me. Nice that it has the side-effect of speeding up a
bit of the upstream CI, as it drops unncessary tests. I also saw your
note in the cover letter that the corresponding Q35 machine types will
be removed in QEMU 10.1. Thanks!
FWIW:
Reviewed-by: Kashyap C
On Thu, Dec 19, 2024 at 03:41:56PM +, Marc Zyngier wrote:
> On Thu, 19 Dec 2024 15:07:25 +,
> Kashyap Chamarthy wrote:
> >
> > On Thu, Dec 19, 2024 at 12:26:29PM +, Marc Zyngier wrote:
> > > On Thu, 19 Dec 2024 11:35:16 +0000,
> > > Kashyap Chama
On Thu, Dec 19, 2024 at 12:26:29PM +, Marc Zyngier wrote:
> On Thu, 19 Dec 2024 11:35:16 +,
> Kashyap Chamarthy wrote:
[...]
> > Consider this:
> >
> > Say, there's a serious security issue in a released ARM CPU. As part of
> > the fix, two new
On Thu, Dec 12, 2024 at 11:04:30AM +0100, Eric Auger wrote:
Hi Eric,
> On 12/12/24 10:36, Cornelia Huck wrote:
> > On Thu, Dec 12 2024, Daniel P. Berrangé wrote:
[...]
> >> Consider you mgmt app wants to set a CPU model that's common across
> >> heterogeneous hardware. They don't neccessarily
On Mon, Nov 04, 2024 at 04:30:17PM +, Peter Maydell wrote:
> On Mon, 4 Nov 2024 at 15:34, Eric Auger wrote:
[...]
> > > If possible, it would be really helpful (and user-friendly) to be able
> > > to specify the CPU feature names as you see under /proc/cpuinfo, and be
> > > able to turn the
(Cross-posted to KVM, Rust-VMM, QEMU, and libvirt lists.)
Hi,
The CFP for the 'Virt & IaaS' (Infrastructure as a Service) 2025
"devroom" is out[+].
- Where? — Brussels, Belgium
- When? — 02 Feb (Sunday) 2025
- Talk submission deadline — 01 Dec 2024
(The CFP submission on the FOSDEM l
On Mon, Oct 28, 2024 at 05:29:11PM +0100, Cornelia Huck wrote:
> On Mon, Oct 28 2024, Daniel P. Berrangé wrote:
[...]
> >> We could consolidate that to the current "host" model, once we figure
> >> out how to handle the currently already existing properties. Models
> >> based on the different ar
On Fri, Oct 25, 2024 at 12:17:40PM +0200, Eric Auger wrote:
> From: Cornelia Huck
>
> Add some documentation for the custom model.
>
> Signed-off-by: Eric Auger
> Signed-off-by: Cornelia Huck
> ---
> docs/system/arm/cpu-features.rst | 55 +++-
> 1 file changed, 47
On Fri, Oct 25, 2024 at 12:17:19PM +0200, Eric Auger wrote:
Hi Eric,
I'm new to Arm, so please bear with my questions :)
> This RFC series introduces a KVM host "custom" model.
(a) On terminology: as we know, in the x86 world, QEMU uses these
terms[1]:
- Host passthrough
- Named CP
On Thu, Jul 18, 2024 at 03:09:37PM +0200, Markus Armbruster wrote:
> Thomas Weißschuh writes:
[...]
> > +#
> > +# @raw: Raw disk image format.
> > +#
> > +# @qcow2: QEMU image format.
>
> It's not the only QEMU image format... Maybe "The QCOW2 image format."
> Almost tautological, but I don't
[Cross-posted to KVM, Rust-VMM, QEMU, and libvirt lists)
Hi, the CFP for the "Virt & IaaS" DevRoom is out[+].
Something new this year is a new talk-submission system: so you need to
create a new account, even if you've had an account with the older
talk-submission system. Details in the "Submit
On Wed, May 31, 2023 at 04:22:34PM +0200, Thomas Huth wrote:
> On 23/05/2023 15.31, Kashyap Chamarthy wrote:
> > Commit 812b31d3f9 (configs: rename default-configs to configs and
> > reorganise, 2021-07-07) did the rename.
> >
> > Reflect that update also in the documen
On Tue, May 23, 2023 at 03:31:17PM +0200, Kashyap Chamarthy wrote:
[I missed to include version history under "---"; now done]
> Commit 812b31d3f9 (configs: rename default-configs to configs and
> reorganise, 2021-07-07) did the rename.
>
> Reflect that update als
Commit 812b31d3f9 (configs: rename default-configs to configs and
reorganise, 2021-07-07) did the rename.
Reflect that update also in the documentation.
Signed-off-by: Kashyap Chamarthy
---
docs/devel/build-system.rst | 12 +--
docs/devel/kconfig.rst | 40
On Fri, May 12, 2023 at 04:09:20PM +0800, Wang, Lei wrote:
> There are also several "default-configs" in docs/devel/kconfig.rst, I think
> they
> can also be updated in this patch.
Good catch, I'll respin it.
> BR,
> Lei
>
> On 10/4/2021 15:12, Kashyap Ch
On Wed, Apr 26, 2023 at 07:20:08PM +0200, Kashyap Chamarthy wrote:
> On Wed, Apr 26, 2023 at 07:40:02PM +0300, Michael Tokarev wrote:
> > 18.04.2023 12:04, Igor Mammedov wrote:
> > > with Q35 using ACPI PCI hotplug by default, user's request to unplug
> > > de
On Wed, Apr 26, 2023 at 07:40:02PM +0300, Michael Tokarev wrote:
> 18.04.2023 12:04, Igor Mammedov wrote:
> > with Q35 using ACPI PCI hotplug by default, user's request to unplug
> > device is ignored when it's issued before guest OS has been booted.
> > And any additional attempt to request device
On Wed, Apr 05, 2023 at 11:42:56AM +0200, Igor Mammedov wrote:
> with Q35 using ACPI PCI hotplug by default, user's request to unplug
> device is ignored when it's issued before guest OS has been booted.
> And any additional attempt to request device hot-unplug afterwards
> results in following err
es ;-)
>
> Who's with me?
Happy to chip in wherever I can be useful :-)
Reviewed-by: Kashyap Chamarthy
> Signed-off-by: Alex Bennée
> Cc: Thomas Huth
> Cc: Daniel P. Berrangé
> Cc: Markus Armbruster
> Cc: Kashyap Chamarthy
> Cc: Paolo Bonzini
> Cc: Peter
.
> +
> +.. code::
> +
> + -drive
> if=pflash,file=(pwd)/pc-bios/edk2-aarch64-code.fd,format=raw,readonly=on \
> + -drive if=pflash,file=$HOME/images/qemu-arm64-efivars,format=raw
Here, -blockdev. (I don't have a replacement invocation off-hand,
afraid.)
Regardless of whether these are addressed, this is a strict improvement:
Reviewed-by: Kashyap Chamarthy
[...]
--
/kashyap
- Add padding to the firmware images. IOW, if the firmware is 2 MB,
add zero-padding to the end of the image to round it upto 4 MB
(whatever you anticipate the largest size wil be in future).
...
(/quote)
[1] https://edk2.groups.io/g/devel/message/54758
Regardless:
Reviewed-by: Kashyap Chamarthy
> ##
> # @FirmwareFlashFile:
> --
> 2.38.1
>
--
/kashyap
(Cc also: libvirt upstream maling list)
Gentle reminder ...
tl;dr: please submit the proposals by *10th Dec 2022*
On Tue, Nov 08, 2022 at 10:45:33AM -0500, Stefan Hajnoczi wrote:
> Hi,
> The yearly FOSDEM open source conference is now accepting talk
> proposals. FOSDEM '23 will be held in Brusse
#x27;, 'verbose-dynamic',
> - 'verbose-static' ] }
> + 'data' : [ 'acpi-s3', 'acpi-s4',
> + 'amd-sev', 'amd-sev-es', 'amd-sev-snp',
> + 'intel-tdx',
> + 'enrolled-keys', 'requires-smm', 'secure-boot',
> + 'verbose-dynamic', 'verbose-static' ] }
With the above tiny nits fixed:
Reviewed-by: Kashyap Chamarthy
> ##
> # @FirmwareFlashFile:
> --
> 2.37.3
>
--
/kashyap
Hi,
You can post questions for the upcoming KVM Forum panel discussion[1] at
Dublin here:
https://etherpad.opendev.org/p/KVMForum_2022_Panel
The session[1] is on 14th September (Wednesday), Dublin, KVM Forum 2022.
The panel is for discussing technical and non-technical topics related
to KVM
Ping.
Thomas/Peter: when you get some time, please have a look at this.
On Mon, Jun 06, 2022 at 06:55:47PM +0200, Kashyap Chamarthy wrote:
> On Mon, Jun 06, 2022 at 06:49:49PM +0200, Kashyap Chamarthy wrote:
> > Oops, messed up v3's cover-letter subject; now fixed. Sorry.
>
&
Hi,
On Wednesday, June 8, 2022, Thomas Huth wrote:
> On 06/06/2022 18.43, Kashyap Chamarthy wrote:
>
>> This document is referred to from the GettingStartedDevelopers wiki
>> which will be rSTified in a follow-up commit.
>>
>> Converted from Mediawiki to rST
On Mon, Jun 06, 2022 at 06:49:49PM +0200, Kashyap Chamarthy wrote:
> Oops, messed up v3's cover-letter subject; now fixed. Sorry.
Sigh, instead of "v3", I accidentally wrote "v4" in the cover-letter
subject. Now fix that too; sorry for the noise.
> On Mon, J
Oops, messed up v3's cover-letter subject; now fixed. Sorry.
On Mon, Jun 06, 2022 at 06:43:32PM +0200, Kashyap Chamarthy wrote:
> - Add back the "" fragment in security-process.rst
> [Thomas]
> - Add a docs/about/contacting-the-project.rst as per Peter's
nversion.
[1] https://wiki.qemu.org/Documentation/GettingStartedDevelopers
Signed-off-by: Kashyap Chamarthy
---
docs/devel/getting-started-developers.rst | 200 ++
docs/devel/index.rst | 1 +
2 files changed, 201 insertions(+)
create mode 100644 docs/
the users
mailing list, as it will be referred to from a different document from
the docs/about/ directory.
Besides that, this is almost a 1-1 conversion (I double-checked to the
best I could). I've also checked that the hyperlinks work correctly
post-conversion.
Signed-off-by: Kashyap C
website".
[1] https://www.qemu.org/support/
[2] https://lists.nongnu.org/archive/html/qemu-devel/2022-03/msg05178.html
Signed-off-by: Kashyap Chamarthy
---
docs/about/contacting-the-project.rst | 16
docs/about/index.rst | 1 +
2 files changed, 17 insertions(+)
crea
ked to the best I could). I've also
checked that the hyperlinks work correctly post-conversion.
[1] https://lists.nongnu.org/archive/html/qemu-devel/2021-11/msg04002.html
[2] https://www.qemu.org/contribute/security-process
Suggested-by: Paolo Bonzini
Signed-off-by: Kashyap Chamarthy
org/Documentation/GettingStartedDevelopers
[4] https://lists.nongnu.org/archive/html/qemu-devel/2021-11/msg04002.html
-------
Kashyap Chamarthy (4):
docs: rSTify "security-process" page; move it to QEMU Git
docs: rSTif
On Wed, May 18, 2022 at 09:04:35AM +0200, Thomas Huth wrote:
> On 15/03/2022 16.54, Kashyap Chamarthy wrote:
> > Missed this during the initial conversion.
> >
> > Signed-off-by: Kashyap Chamarthy
> > ---
> > This patch should be merged on top of this[1]. O
On Tue, Apr 26, 2022 at 08:55:38AM +0100, Daniel P. Berrangé wrote:
> On Mon, Apr 25, 2022 at 02:19:27PM -0400, John Snow wrote:
> > On Mon, Apr 25, 2022, 6:56 AM Daniel P. Berrangé
> > wrote:
> >
> > > On Fri, Apr 22, 2022 at 02:49:32PM -0400, John Snow wrote:
> > > > Point to this library's URL
-
> MANIFEST.in | 1 -
> 2 files changed, 13 insertions(+), 37 deletions(-)
> rename README.rst => FILES.rst (64%)
As usual, thanks for the care for documentation.
Reviewed-by: Kashyap Chamarthy
[...]
--
/kashyap
e future.
>
> So long as --keep-outdated is always passed to Pipenv, items that aren't
> absolutely necessary to update will not be, which will help keep our
> requirements more at the very oldest possible versions that still work.
>
> Signed-off-by: John Snow
Makes sense.
On Mon, Apr 04, 2022 at 02:56:10PM -0400, John Snow wrote:
> On Mon, Apr 4, 2022 at 2:54 PM John Snow wrote:
[...]
> > > > .gitignore | 2 +-
> > > > Makefile | 16
> > > > setup.cfg | 24 +---
> > > > setup.py | 2 +-
> > > > 4 files changed, 11 inse
gt; +name = qemu.qmp
> version = file:VERSION
> maintainer = QEMU Developer Team
In the spirit of patch 04 ("update maintainer metadata"), do you also
want to update here too? s/QEMU Developer Team/QEMU Project?
FWIW:
Reviewed-by: Kashyap Chamarthy
[...]
--
/kashyap
On Wed, Mar 30, 2022 at 02:24:20PM -0400, John Snow wrote:
> The README here will reflect both what is shown on GitLab and on the
> PyPI landing page. Update it accordingly, and freshen it up.
>
> FIXME: Update URLs when pushing to the production repo.
>
> Suggested-by:
On Mon, Mar 21, 2022 at 11:01:28AM +, Peter Maydell wrote:
> On Mon, 21 Mar 2022 at 09:55, Kashyap Chamarthy wrote:
[...]
> > > Yes, I think that about/ should have a document something like
> > > "Contacting the project" or "Support", which could t
On Tue, Mar 15, 2022 at 04:12:50PM +, Peter Maydell wrote:
> On Tue, 15 Mar 2022 at 16:00, Kashyap Chamarthy wrote:
> >
> > On Tue, Mar 15, 2022 at 02:25:05PM +0100, Thomas Huth wrote:
> > > On 14/03/2022 11.49, Kashyap Chamarthy wrote:
> >
> > [...]
&g
On Tue, Mar 15, 2022 at 02:25:05PM +0100, Thomas Huth wrote:
> On 14/03/2022 11.49, Kashyap Chamarthy wrote:
[...]
> At least the "users" mailing list is not related to development, so maybe
> this should rather go into docs/about/ instead?
Yeah, makes sense. I wonder if
Missed this during the initial conversion.
Signed-off-by: Kashyap Chamarthy
---
This patch should be merged on top of this[1]. Otherwise Sphinx will
complain (correctly so).
[1] https://lists.nongnu.org/archive/html/qemu-devel/2022-03/msg03488.html
-- docs: rSTify MailingLists wiki; move
On Tue, Mar 15, 2022 at 01:47:38PM +0100, Thomas Huth wrote:
> On 14/03/2022 11.49, Kashyap Chamarthy wrote:
[...]
> > + - Once the patch is merged, close the upstream bug with a link to
> > + the commit
> > +
> > + - Fixed in:
>
> There used to
On Mon, Mar 14, 2022 at 02:45:30PM +0100, Philippe Mathieu-Daudé wrote:
> Hi Kashyap,
Hi,
> On 14/3/22 11:49, Kashyap Chamarthy wrote:
[...]
> This is a fair conversion from
> https://wiki.qemu.org/Contribute/MailingLists, but a good opportunity to
> improve (could be
nversion.
[1] https://wiki.qemu.org/Documentation/GettingStartedDevelopers
Signed-off-by: Kashyap Chamarthy
---
docs/devel/getting-started-developers.rst | 200 ++
docs/devel/index.rst | 1 +
2 files changed, 201 insertions(+)
create mode 100644 docs/
I could). I've also
checked that the hyperlinks work correctly post-conversion.
Signed-off-by: Kashyap Chamarthy
---
docs/devel/index.rst | 1 +
docs/devel/mailing-lists.rst | 53
2 files changed, 54 insertions(+)
create mode 100644 docs/
ked to the best I could). I've also
checked that the hyperlinks work correctly post-conversion.
[1] https://lists.nongnu.org/archive/html/qemu-devel/2021-11/msg04002.html
[2] https://www.qemu.org/contribute/security-process
Suggested-by: Paolo Bonzini
Signed-off-by: Kashyap Chamarthy
iki.
[1] https://www.qemu.org/contribute/security-process
[2] https://wiki.qemu.org/Contribute/MailingLists
[3] https://wiki.qemu.org/Documentation/GettingStartedDevelopers
[4] https://lists.nongnu.org/archive/html/qemu-devel/2021-11/msg04002.html
Kashyap Chamarthy (3):
docs: rSTify "security-pr
/patch:113: trailing whitespace.
.git/rebase-apply/patch:136: trailing whitespace.
.git/rebase-apply/patch:61: new blank line at EOF.
+
warning: squelched 3 whitespace errors
warning: 8 lines add whitespace errors.
FWIW:
Reviewed-by: Kashyap Chamarthy
[...]
--
/kashyap
On Fri, Feb 25, 2022 at 12:08:28PM -0500, John Snow wrote:
> Mea culpa. Dan's patch wound up with the wrong import path because I
> re-ordered my most recent pull request and missed that this needed a fix
> on rebase.
>
> Fixes: 43912529
> Reported-by: Kashyap Chamarthy
On Thu, Feb 17, 2022 at 12:07:15PM +1100, Ben Smith wrote:
> Hi All,
Hi,
> I'm cross-posting this from Reddit qemu_kvm, in case it helps in some
> way. I know my setup is ancient and unique; let me know if you would
> like more info.
>
> Symptoms:
> 1. Ubuntu10.04 32-bit guest locks up randomly b
On Thu, Feb 17, 2022 at 08:57:19AM +0100, Thomas Huth wrote:
> On 16/02/2022 18.40, Dr. David Alan Gilbert wrote:
[...]
> > So just adding something like the following under 'System emulator
> > machines':
> >
> > x86 default machine type
> >
> >
> > x86 currently defau
On Tue, Jan 25, 2022 at 10:20:11AM +0100, Gerd Hoffmann wrote:
> Hi,
>
> > IMHO the ideal scenario would be for us to have a kernel, initrd
> > containing just busybox tools for the key arch targets we care
> > about. Those could be used with direct kernel boot or stuffed
> > into a disk iamge.
On Mon, Jan 31, 2022 at 03:35:02PM +, Daniel P. Berrangé wrote:
> On Mon, Jan 31, 2022 at 04:21:36PM +0100, Kashyap Chamarthy wrote:
> > On Mon, Jan 31, 2022 at 02:36:46PM +, Daniel P. Berrangé wrote:
[...]
> > > The firmware can be provided in qcow2 format
On Mon, Jan 31, 2022 at 02:36:46PM +, Daniel P. Berrangé wrote:
> On Mon, Jan 31, 2022 at 03:00:33PM +0100, Kashyap Chamarthy wrote:
> > On Mon, Jan 31, 2022 at 12:55:09PM +, Daniel P. Berrangé wrote:
[...]
> > I briefly wondered if in this "combined"
cutable. The firmware
> -# executable may be shared by multiple virtual machine
> -# definitions. The preferred corresponding QEMU command
> -# line options are
> +# @mode: describes how the firmware build handles code versus variable
> +#storage. If not present, it must be treated as if it was
> +#configured with value ``split``. Since: 7.0.0
For consistency, might want to capitalize the first word:
s/describes/Describes/
(Here too, maintainer can touch it up.)
[...]
The concept looks very clear, and obviously useful. FWIW:
Reviewed-by: Kashyap Chamarthy
> --
> 2.34.1
>
--
/kashyap
Hi,
(Sorry for the slowness here.)
On Thu, Jan 20, 2022 at 12:45:02PM +0100, Kevin Wolf wrote:
> Am 20.01.2022 um 09:02 hat Pierre Libeau geschrieben:
[...]
> > Hello,
> >
> > I'm working on a patch in nova to improve the time of file system
> > freeze during live-snapshot on an instance with
On Mon, Nov 29, 2021 at 01:35:11PM +, Peter Maydell wrote:
> On Wed, 24 Nov 2021 at 14:27, Kashyap Chamarthy wrote:
[...]
> > [1] https://lists.nongnu.org/archive/html/qemu-devel/2021-11/msg04002.html
> > [2] https://www.qemu.org/contribute/report-a-bug/
> >
> >
On Wed, Nov 24, 2021 at 08:35:35PM +0100, Paolo Bonzini wrote:
> On 11/19/21 11:15, Kashyap Chamarthy wrote:
> > Noted; so these two pages:
> >
> > -https://www.qemu.org/contribute/security-process/
> > -https://www.qemu.org/contribute/report-a-bug/
I posted
'index.rst' to to reflect
that the manual also documents some of QEMU's development processes.
[1] https://lists.nongnu.org/archive/html/qemu-devel/2021-11/msg04002.html
[2] https://www.qemu.org/contribute/report-a-bug/
Suggested-by: Paolo Bonzini
Signed-off-by: Kashyap Chamarthy
ked to the best I could). I've also
checked that the hyperlinks work correctly post-conversion.
[1] https://lists.nongnu.org/archive/html/qemu-devel/2021-11/msg04002.html
[2] https://www.qemu.org/contribute/security-process
Suggested-by: Paolo Bonzini
Signed-off-by: Kashyap Chamarth
t because, we refer to
it from 'reporting-a-bug'. (If we reverse the order, the build fails --
correctly so.)
[1] https://www.qemu.org/contribute/report-a-bug/
[2] https://www.qemu.org/contribute/security-process
[3] https://lists.nongnu.org/archive/html/qemu-devel/2021-11/msg04002.
On Mon, Nov 22, 2021 at 03:01:58PM +0100, Thomas Huth wrote:
> On 22/11/2021 14.53, Peter Maydell wrote:
[...]
> > I don't think we should be recommending to new contributors that
> > they do things that established contributors generally do not do.
> > The document has enough "things you should
On Mon, Nov 22, 2021 at 01:36:53PM +0100, Thomas Huth wrote:
> On 22/11/2021 13.19, Kashyap Chamarthy wrote:
[...]
> > I kept that because an explicit reminder about spell-check is useful;
> > it's easy to forget. Another option is to retain the line, but replace
>
On Mon, Nov 22, 2021 at 11:36:54AM +0100, Thomas Huth wrote:
> On 22/11/2021 11.20, Kashyap Chamarthy wrote:
> > On Mon, Nov 22, 2021 at 10:51:15AM +0100, Thomas Huth wrote:
[...]
> > > I'll add the link to https://wiki.qemu.org/Contribute/SpellCheck again.
>
On Mon, Nov 22, 2021 at 10:51:15AM +0100, Thomas Huth wrote:
> On 19/11/2021 20.31, Kashyap Chamarthy wrote:
> > I completely botched up the merged[0] rST conversion of this document by
> > accidentally dropping entire hunks (!) of text. :-( I made it very hard
> > for rev
Add some more examples of commonly used commit-message tags.
(Thanks: Alex Bennée)
Signed-off-by: Kashyap Chamarthy
---
docs/devel/submitting-a-patch.rst | 4
1 file changed, 4 insertions(+)
diff --git a/docs/devel/submitting-a-patch.rst
b/docs/devel/submitting-a-patch.rst
index
ki[1] page from scratch and replaced the existing rST with it, while
making sure I incorporated previous feedback. Sorry for the sloppiness.
More details in patch-1.
[0] https://gitlab.com/qemu-project/qemu/-/commit/9f73de8df033
Kashyap Chamarthy (2):
docs: Fix botched rST conversion of &#x
te/SubmitAPatch&oldid=10387
[2] https://lists.nongnu.org/archive/html/qemu-devel/2021-11/msg03600.html
Signed-off-by: Kashyap Chamarthy
---
docs/devel/submitting-a-patch.rst | 198 ++
1 file changed, 149 insertions(+), 49 deletions(-)
diff --git a/docs/deve
On Fri, Nov 19, 2021 at 10:09:27AM +0100, Paolo Bonzini wrote:
[...]
> Hi, I'm applying instead
> https://lore.kernel.org/r/2028074702.216951-2-pbonzini%40redhat.com
> (sorry, you couldn't know of the magic redirect since that's done directly
> on shell.qemu.org's Apache configuration).
Ah,
We've recently converted[1] the "SubmitAPatch" page from Wiki to in-tree
docs. So update the website to reflect this.
[1] https://gitlab.com/qemu-project/qemu/-/commit/9f73de8df03 --
9f73de8df0 (docs: rSTify the "SubmitAPatch" wiki, 2021-11-10)
Signed-
On Wed, Nov 17, 2021 at 03:43:56PM +0100, Thomas Huth wrote:
> On 17/11/2021 11.25, Kashyap Chamarthy wrote:
[...]
> > > That ".". looks a little bit weird in the output ... maybe we should
> > > replace
> > > it with "does not end with a dot."
On Wed, Nov 17, 2021 at 10:08:52AM +0100, Thomas Huth wrote:
> On 10/11/2021 15.49, Kashyap Chamarthy wrote:
[...]
> > writing-qmp-commands
> > trivial-patches
> > submitting-a-pull-request
> > + submitting-a-patch
>
> I'd suggest to ins
you can find all
the authors in the wiki history[3].
[1] https://wiki.qemu.org/Contribute/SubmitAPatch
[2] http://wiki.qemu.org/index.php?title=Contribute/SubmitAPatch&action=edit
[3] http://wiki.qemu.org/index.php?title=Contribute/SubmitAPatch&action=history
Signed-off-by: Kashyap Cham
://wiki.qemu.org/Contribute/SubmitAPullRequest
Signed-off-by: Kashyap Chamarthy
---
docs/devel/index.rst | 1 +
docs/devel/submitting-a-pull-request.rst | 76
2 files changed, 77 insertions(+)
create mode 100644 docs/devel/submitting-a-pull-request.rst
diff
itAPatch wiki page
- Convert the KeySigningParty wiki to rST
- Update the links to point to the rST-generated HTML files, instead of
wiki
Kashyap Chamarthy (3):
docs: rSTify the "TrivialPatches" wiki
docs: rSTify the "SubmitAPullRequest" wiki
docs: rSTify the &quo
flect current reality.
[1] https://wiki.qemu.org/Contribute/TrivialPatches
Signed-off-by: Kashyap Chamarthy
---
docs/devel/index.rst | 1 +
docs/devel/trivial-patches.rst | 50 ++
2 files changed, 51 insertions(+)
create mode 100644 docs/devel/tr
On Fri, Oct 15, 2021 at 05:22:59PM +0200, Kashyap Chamarthy wrote:
> - Remove stray texinfo syntax (remnants of texinfo to rST conversion)
> - Clarify the bit about long-term stable CPU models
>
> TODO: In a future patch, include potential examples as discussed
> here[1].
On Mon, Nov 08, 2021 at 04:16:56PM +0100, Thomas Huth wrote:
> On 02/11/2021 16.51, Kashyap Chamarthy wrote:
> > On Mon, Nov 01, 2021 at 02:56:43PM +, Peter Maydell wrote:
> > > On Tue, 19 Oct 2021 at 10:04, Kashyap Chamarthy
> > > wrote:
> > > >
&g
1 - 100 of 538 matches
Mail list logo
