[Xen-devel] Added workflow docs for git-series

See https://wiki.xenproject.org/wiki/Managing_Xen_Patches_with_Git-series It solves some problems with git and makes managing series a little easier, but you still have to use autosquash So, it's not perfect Lars ___ Xen-devel mailing list Xen-devel@li

[Xen-devel] [PATCH v3 2/3] Add V section entry to allow identification of Xen MAINTAINERS file

Signed-off-by: Lars Kurth --- MAINTAINERS | 4 1 file changed, 4 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 77413e0..bb3da43 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -97,6 +97,9 @@ Descriptions of section entries

[Xen-devel] [PATCH v3 1/3] Remove hardcoding from scripts/add_maintainers.pl

Instead of using a hardcoded location, inherit the location from $0 Signed-off-by: Lars Kurth --- scripts/add_maintainers.pl | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/add_maintainers.pl b/scripts/add_maintainers.pl index 09e9f66..5a6d0f6 100755 --- a

[Xen-devel] [PATCH v3 0/3] Allow get_maintainer.pl / add_maintainers.pl scripts to be called outside of xen.git

Changes in v2: * Remove debug message Changes in v3: * Split patch * add_maintainers.pl: do not issue a warning * add_maintainers.pl: introduce processing logic for V: tag * MAINTAINERS: Add V: tag to file Lars Kurth (3): Remove hardcoding

[Xen-devel] [PATCH v3 3/3] Add logic to use V section entry in THE REST for identifying xen trees

Specifically: * Move check until after the MAINTAINERS file has been read * Add get_xen_maintainers_file_version() for check * Remove top_of_tree as not needed any more * Faiul with extended error message when used out of tree Signed-off-by: Lars Kurth --- scripts/get_maintainer.pl | 58

Re: [Xen-devel] [PATCH v3 3/3] Add logic to use V section entry in THE REST for identifying xen trees

On 02/09/2019, 09:08, "Jan Beulich" wrote: On 30.08.2019 22:09, Lars Kurth wrote: > Specifically: > * Move check until after the MAINTAINERS file has been read > * Add get_xen_maintainers_file_version() for check > * Remove top_of_tree as not needed

Re: [Xen-devel] [RFC] Code of Conduct

On 02/09/2019, 16:49, "Ian Jackson" wrote: Lars Kurth writes ("Re: [Xen-devel] [RFC] Code of Conduct"): > I attached a redline version of both the original (based on the LF events CoC) and a redline version based on the covenant given the constraints we agreed

[Xen-devel] Please propose agenda items for Thursday's community call

Folks, I have not gotten around to draft an agenda yet. Please reply to this thread with possible agenda items. I will reply to this thread with meeting invite and details as usual Regards Lars ___ Xen-devel mailing list Xen-devel@lists.xenproject.org h

[Xen-devel] [PATCH v4 3/3] Add logic to use V section entry in THE REST for identifying xen trees

Specifically: * Move check until after the MAINTAINERS file has been read * Add get_xen_maintainers_file_version() for check * Remove top_of_tree as not needed any more * Fail with extended error message when used out of tree Signed-off-by: Lars Kurth --- scripts/get_maintainer.pl | 57

[Xen-devel] [PATCH v4 2/3] Add V section entry to allow identification of Xen MAINTAINERS file

Signed-off-by: Lars Kurth Acked-by: Jan Beulich --- MAINTAINERS | 4 1 file changed, 4 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 77413e0..bb3da43 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -97,6 +97,9 @@ Descriptions of section

[Xen-devel] [PATCH v4 0/3] Allow get_maintainer.pl / add_maintainers.pl scripts to be called outside of xen.git

and fixed typo * Removed unused variable Lars Kurth (3): Remove hardcoding from scripts/add_maintainers.pl Add V section entry to allow identification of Xen MAINTAINERS file Add logic to use V section entry in THE REST for identifying xen trees MAINTAINERS| 4

[Xen-devel] [PATCH v4 1/3] Remove hardcoding from scripts/add_maintainers.pl

Instead of using a hardcoded location, inherit the location from $0 Signed-off-by: Lars Kurth --- scripts/add_maintainers.pl | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/add_maintainers.pl b/scripts/add_maintainers.pl index 09e9f66..5a6d0f6 100755 --- a

Re: [Xen-devel] Please propose agenda items for Thursday's community call

On 04/09/2019, 13:35, "Jan Beulich" wrote: On 03.09.2019 20:37, Lars Kurth wrote: > I have not gotten around to draft an agenda yet. Please reply to > this thread with possible agenda items. I will reply to this > thread with meeting invite and details as

[Xen-devel] [ANNOUNCE] Call for agenda items for September 5th Community Call @ 15:00 UTC

Hi all, the proposed agenda is in https://cryptpad.fr/pad/#/2/pad/edit/xwUTm6b5f5ijPTQcF9IFgkBg/ and you can edit to add items Alternatively, you can reply to this mail directly Agenda items appreciated ASAP: please put your name besides items if you edit the document Apologies for dropping th

[Xen-devel] [Poll] Please vote on date options for next year's Developer Summit (closes Wednesday, September 11)

Hi all, we started planning next year’s Developer Summit, which is due to be in Europe. We have a venue in Bucharest, Romania secured but are still working through the details. As we are early, we do have several date options: so I wanted to give you a choice to vote, such that we end up with a

[Xen-devel] [PATCH] Import v1.4 of Contributor Covenant CoC

Signed-off-by: Lars Kurth --- Cc: minios-de...@lists.xenproject.org Cc: xen-...@lists.xenproject.org Cc: win-pv-de...@lists.xenproject.org Cc: mirageos-de...@lists.xenproject.org Cc: committ...@xenproject.org --- code-of-conduct.md | 76 ++ 1

[Xen-devel] [PATCH 0/2] Code of Conduct (based on Contributor Covenant v1.4)

/CoC-v1 Cc: minios-de...@lists.xenproject.org Cc: xen-...@lists.xenproject.org Cc: win-pv-de...@lists.xenproject.org Cc: mirageos-de...@lists.xenproject.org Cc: committ...@xenproject.org Lars Kurth (2): Import v1.4 of Contributor Covenant CoC Xen Project Code of Conduct -- 2.13.0

[Xen-devel] [PATCH] Xen Project Code of Conduct

* Replace "project team" with "Conduct Team members" * Add e-mail alias * Add section on contacting individual Conduct Team members * Add section on Conduct Team members Signed-off-by: Lars Kurth --- Cc: minios-de...@lists.xenproject.org Cc: xen-...@lists.xenproject.org Cc: win-pv

Re: [Xen-devel] [PATCH 0/2] Code of Conduct (based on Contributor Covenant v1.4)

On 04/09/2019, 19:12, "Lars Kurth" wrote: This series proposes a concrete version of the Xen Project CoC based on v1.4 of the Contributor Covenant. See [1] Apologies for the badly formatted patch. It seems the normal instructions do not work when using it on virgin git

Re: [Xen-devel] [ANNOUNCE] Call for agenda items for September 5th Community Call @ 15:00 UTC

On 05/09/2019, 08:41, "Rich Persaud" wrote: > On Sep 5, 2019, at 03:19, Jan Beulich wrote: > > Forgive me asking, but why is this put up as an agenda item here? > IMO this is the kind of thing where you would send a proposal and > request feedback by email first, and put

Re: [Xen-devel] [ANNOUNCE] Call for agenda items for September 5th Community Call @ 15:00 UTC

On 05/09/2019, 08:50, "Jan Beulich" wrote: On 05.09.2019 09:41, Rich Persaud wrote: > If Xen community call topics are limited to escalations of xen-devel threads, then a new thread can be created for this topic. Xen community calls have also provided real-time, interactive feedback

Re: [Xen-devel] [ANNOUNCE] Call for agenda items for September 5th Community Call @ 15:00 UTC

On 05/09/2019, 09:33, "Juergen Gross" wrote: On 05.09.19 10:14, Andrew Cooper wrote: > On 05/09/2019 08:49, Lars Kurth wrote: >> On 05/09/2019, 08:41, "Rich Persaud" wrote: >> >> > On Sep 5, 2019, at 03:19, Jan Beulich w

Re: [Xen-devel] [ANNOUNCE] Call for agenda items for September 5th Community Call @ 15:00 UTC

> We can defer the xenstoreless name service topic to the October monthly call. > > For today's call, can we discuss the previously posted high-level design for > unification of the domB RFC with dom0less, as "domB mode" for > disaggregation of Xen's dom0? > > - domB mode for dom0less (July 2019)

Re: [Xen-devel] [PATCH] docs/sphinx: todo/wishlist

CC: Stefano Stabellini CC: Tim Deegan CC: Wei Liu CC: Julien Grall CC: Lars Kurth CC: Paul Durrant CC: Roger Pau Monné RFC for obvious reasons. A rendered version of this can be found at: https://andrewcoop-xen.readthedocs.io/en/docs-wi

Re: [Xen-devel] [ANNOUNCE] Minutes for September 5th Community Call

Minutes are at https://cryptpad.fr/pad/#/2/pad/view/kpV4XxFWKjAF1fbIckIV87BVTRVRFlL913YWaFD0waI/embed/present/ and attached Lars 2019-09 Community Call.pdf Description: 2019-09 Community Call.pdf ___ Xen-devel mailing list Xen-devel@lists.xenproject.

Re: [Xen-devel] Criteria for checking in core scheduling series

On 06/09/2019, 12:09, "George Dunlap" wrote: There was a discussion on the community call about the core scheduling series being developed by Juergen Gross [1]. The conclusion can be summarized as follows: * We normally wait to check in series until they are quite good --

Re: [Xen-devel] [PATCH] Xen Project Code of Conduct

On 06/09/2019, 16:10, "Roger Pau Monne" wrote: On Wed, Sep 04, 2019 at 07:12:18PM +0100, Lars Kurth wrote: [...] > +## Conduct Team members > +Conduct Team members are project leadership team members from any > +sub-project. The current list of Cond

[Xen-devel] [Vote] XCP-ng subproject proposal

Hello everyone, Olivier had posted an RFC for this proposal on xen-devel@- see https://xen.markmail.org/thread/ermnrb3ps3okvnjr The proposal also has been discussed by the Advisory Board and was approved However, for the proposal to fully pas

Re: [Xen-devel] [PATCH v4 2/3] Add V section entry to allow identification of Xen MAINTAINERS file

On 10/09/2019, 16:31, "Julien Grall" wrote: Hi, Actually, I have one question about the template (my ack still stands). On 9/10/19 4:18 PM, Julien Grall wrote: > Hi Lars, > > On 9/4/19 12:30 PM, Lars Kurth wrote: >> This c

[Xen-devel] [livepatch-build-tools] Add V: entry to maintainers

Usage of get_maintainers.pl now requires the V: entry under THE REST to identify a MAINTAINERS file in one of the Xen trees. See [1] [1] lists.xenproject.org/archives/html/xen-devel/2019-09/threads.html#00263 Signed-off-by: Lars Kurth --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff

[Xen-devel] [PATCH OSSTEST] Introduce a MAINTAINERS file

Rationale: this will allow us to use get_maintainer.pl / add_maintainers.pl scripts from xen.git Signed-off-by: Lars Kurth --- MAINTAINERS | 11 +++ 1 file changed, 11 insertions(+) create mode 100644 MAINTAINERS diff --git a/MAINTAINERS b/MAINTAINERS new file mode 100644 index

[Xen-devel] [PATCH XTF] Introduce a MAINTAINERS file

Rationale: this will allow us to use get_maintainer.pl / add_maintainers.pl scripts from xen.git Signed-off-by: Lars Kurth --- MAINTAINERS | 11 +++ 1 file changed, 11 insertions(+) create mode 100644 MAINTAINERS diff --git a/MAINTAINERS b/MAINTAINERS new file mode 100644 index

Re: [Xen-devel] [PATCH] create-diff-object: more precisely identify .rodata sections

On 18/09/2019, 11:44, "Wieczorkiewicz, Pawel" wrote: > On 18. Sep 2019, at 12:41, Ian Jackson wrote: > > Julien Grall writes ("Re: [PATCH] create-diff-object: more precisely identify .rodata sections"): >> On 18/09/2019 10:52, Wieczorkiewicz, Pawel wrote: >>> $ scripts/.

Re: [Xen-devel] [PATCH] create-diff-object: more precisely identify .rodata sections

On 18/09/2019, 12:15, "Julien Grall" wrote: Hi Ian, On 18/09/2019 11:41, Ian Jackson wrote: > Julien Grall writes ("Re: [PATCH] create-diff-object: more precisely identify .rodata sections"): >> On 18/09/2019 10:52, Wieczorkiewicz, Pawel wrote: >>> $ scripts/./add_mai

Re: [Xen-devel] [PATCH] create-diff-object: more precisely identify .rodata sections

On 18/09/2019, 12:27, "Wieczorkiewicz, Pawel" wrote: > On 18. Sep 2019, at 13:19, Julien Grall wrote: > > Hi Pawel, > > On 18/09/2019 11:44, Wieczorkiewicz, Pawel wrote: >>> On 18. Sep 2019, at 12:41, Ian Jackson wrote: >>> >>> Julien Grall writes

[Xen-devel] add_maintainers.pl issues / "canonical" subject prefixes for CI v2 (was Re: [PATCH] create-diff-object: more precisely identify .rodata sections)

+Ross + Doug On 19/09/2019, 10:30, "Julien Grall" wrote: Hi Lars, On 18/09/2019 13:14, Lars Kurth wrote: > > > On 18/09/2019, 12:15, "Julien Grall" wrote: > > Hi Ian, > > On 18/09/2019 11:4

[Xen-devel] Moving next week's community call to Thu 10th

Hi all, because many of us will be at the Platform Security Summit next week, I propose to move the community call to Thu 10th at the usual time Regards Lars ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/l

[Xen-devel] [PATCH v2 4/6] Add Code Review Guide

From: Lars Kurth This document highlights what reviewers such as maintainers and committers look for when reviewing code. It sets expectations for code authors and provides a framework for code reviewers. Signed-off-by: Lars Kurth --- Cc: minios-de...@lists.xenproject.org Cc: xen

[Xen-devel] [PATCH v2 5/6] Add guide on Communication Best Practice

From: Lars Kurth This guide covers the bulk on Best Practice related to code review It primarily focusses on code review interactions It also covers how to deal with Misunderstandings and Cultural Differences Signed-off-by: Lars Kurth --- Cc: minios-de...@lists.xenproject.org Cc: xen

[Xen-devel] [PATCH v2 6/6] Added Resolving Disagreement

From: Lars Kurth This guide provides Best Practice on identifying and resolving common classes of disagreement Signed-off-by: Lars Kurth -- Cc: minios-de...@lists.xenproject.org Cc: xen-...@lists.xenproject.org Cc: win-pv-de...@lists.xenproject.org Cc: mirageos-de...@lists.xenproject.org Cc

[Xen-devel] [PATCH v2 3/6] Add Communication Guide

From: Lars Kurth This document is a portal page that lays out our gold standard, best practices for some common situations and mechanisms to help resolve issues that can have a negative effect on our community. Detail is covered in subsequent documents Signed-off-by: Lars Kurth --- Cc: minios

[Xen-devel] [PATCH v2 0/6] Code of Conduct + Extra Guides and Best Practices

From: Lars Kurth This series proposes a concrete version of the Xen Project CoC based on v1.4 of the Contributor Covenant. See [1] It contains *ALL* the portions I was still going to add. I spent a bit of time on word-smithing, but I am not a native English speaker So there is probably time for

[Xen-devel] [PATCH v2 1/6] Import v1.4 of Contributor Covenant CoC

From: Lars Kurth Signed-off-by: Lars Kurth --- Cc: minios-de...@lists.xenproject.org Cc: xen-...@lists.xenproject.org Cc: win-pv-de...@lists.xenproject.org Cc: mirageos-de...@lists.xenproject.org Cc: committ...@xenproject.org --- code-of-conduct.md | 76

[Xen-devel] [PATCH v2 2/6] Xen Project Code of Conduct

From: Lars Kurth Specific changes to the baseline: * Replace list of positive behaviors with link to separate process * Replace maintainers with project leadership (except in our pledge where maintainers is more appropriate) * Add 'of all sub-projects' to clarify scope of Co

Re: [Xen-devel] [PATCH v2 5/6] Add guide on Communication Best Practice

On 27/09/2019, 09:59, "Jan Beulich" wrote: On 26.09.2019 21:39, Lars Kurth wrote: > +### Express appreciation > +As the nature of code review to find bugs and possible issues, it is very easy for > +reviewers to get into a mode of operation where the p

Re: [Xen-devel] [PATCH v2 5/6] Add guide on Communication Best Practice

On 27/09/2019, 10:14, "Jan Beulich" wrote: On 26.09.2019 21:39, Lars Kurth wrote: > +### Verbose vs. terse > +Due to the time it takes to review and compose code reviewer, reviewers often adopt a > +terse style. It is not unusual to see review comments su

Re: [Xen-devel] [PATCH v2 5/6] Add guide on Communication Best Practice

On 27/09/2019, 11:17, "Lars Kurth" wrote: On 27/09/2019, 10:14, "Jan Beulich" wrote: On 26.09.2019 21:39, Lars Kurth wrote: > +### Verbose vs. terse > +Due to the time it takes to review and compose code reviewer

Re: [Xen-devel] [Vote] XCP-ng subproject proposal

> On 9 Sep 2019, at 15:44, Lars Kurth wrote: > > Hello everyone, > > Olivier had posted an RFC for this proposal on xen-devel@- see > https://xen.markmail.org/thread/ermnrb3ps3okvnjr > <https://xen.markmail.org/thread/ermnrb3ps3okvnjr> > > The propos

[Xen-devel] [ANNOUNCE] Call for agenda items for Oct, 10th Community Call @ 15:00 UTC - One week later than normal

Hi all, the proposed agenda is in https://cryptpad.fr/pad/#/2/pad/edit/4FGEw81flPUiivkjkuvQJ-CK/embed/present/and you can edit to add items Alternatively, you can reply to this mail directly Agenda items appreciated a few days before the call: please put your name besides items if you edit the

Re: [Xen-devel] [VOTE] tagging for operational messages sent to xen-devel@ (was Re: Xen 4.13 Development Update)

Hi all, I almost dropped this: apologies. With the votes in, we have a clear winner for [ANNOUNCE] over the other options ANNOUNCE1 2 2 OPERATIONS -1 -1 1 PROCESS 0 0 -2 Lars On 26/04/2019, 03:50, "Jan Beulich" wrote: >>> On 25.04.19 at 18:

Re: [Xen-devel] [VOTE] tagging for operational messages sent to xen-devel@ (was Re: Xen 4.13 Development Update)

Rich, as nobody replied to the mail, I am inclined to dismiss the proposal of ANN for now Lars > On 25 Apr 2019, at 16:59, Rich Persaud wrote: > >> On Apr 25, 2019, at 12:36, Lars Kurth wrote: >> >> Alright, >> >> there was a lengthy discussion on t

[Xen-devel] No community call this week, but next week

Hi all, I forgot to update my calendar to reflect for the new community call time and thus forgot to ask for agenda items. Sincere apologies. So I propose we have the meeting next week. Will send out agenda requests tomorrow Lars ___ Xen-devel mailing l

Re: [Xen-devel] [VOTE] tagging for operational messages sent to xen-devel@ (was Re: Xen 4.13 Development Update)

On 01/05/2019, 12:56, "Rich Persaud" wrote: > On May 1, 2019, at 14:37, Lars Kurth wrote: > > Rich, > as nobody replied to the mail, I am inclined to dismiss the proposal of ANN for now > Lars What do you think about the suggestion

Re: [Xen-devel] [PATCH] sched/credit: avoid priority boost for capped domains when unpark

> On 3 May 2019, at 10:48, Dario Faggioli wrote: > > On Fri, 2019-05-03 at 15:38 +, Eslam Elnikety wrote: >> When unpausing a capped domain, the scheduler currently clears the >> CSCHED_FLAG_VCPU_PARKED flag before vcpu_wake(). This, in turn, >> causes the >> vcpu_wake to set CSCHED_PRI_TS_

[Xen-devel] [ANNOUNCE] Xen Project Community Call May 9th @15:00 UTC Call for agenda items

Hi all, Please propose topics by either editing the running agenda document at https://docs.google.com/document/d/1ktN-5u8uScEvhf9N8Um5o6poF12lVEnnySHJw_7Jk8k/edit# or by replying to the mail. Ideally by Wednesday! Best Regards Lars == Dial-in Information == ## Meeting time 15:00 - 16:00 UT

Re: [Xen-devel] [ANNOUNCE] Xen Project Community Call May 9th @15:00 UTC Call for agenda items

> On 6 May 2019, at 09:11, Woods, Brian wrote: > > On Mon, May 06, 2019 at 07:51:17AM -0600, Lars Kurth wrote: >> [CAUTION: External Email] >> >> Hi all, >> >> Please propose topics by either editing the running agenda document at >

Re: [Xen-devel] [ANNOUNCE] Xen Project Community Call May 9th @15:00 UTC Call for agenda items

I added these to the agenda https://docs.google.com/document/d/1ktN-5u8uScEvhf9N8Um5o6poF12lVEnnySHJw_7Jk8k/edit# <https://docs.google.com/document/d/1ktN-5u8uScEvhf9N8Um5o6poF12lVEnnySHJw_7Jk8k/edit#> Feel free to add to it Lars > On 6 May 2019, at 09:23, Lars Kurth wrote: > &

[Xen-devel] Guest Testing in OSSTEST - What distros and versions should we test against

Hi all, following a discussion with committers about Guest testing in OSSTEST, it surfaced that we have not updated what distros we test in OSSTEST for a very long time. All agreed that we should regularly review what we test against: maybe at the beginning of a release cycle In any case, curr

Re: [Xen-devel] Guest Testing in OSSTEST - What distros and versions should we test against

> On 10 May 2019, at 01:48, Jan Beulich wrote: >> >> With regards to Windows testing we have some restrictions. We have tried >> several times to buy additional test licenses, but this never went anywhere >> (some of the VM licenses are not available for our environment, unless you >> bulk b

[Xen-devel] RFC: File format to allow us to track imported files

Hi all, following the recent discussion, we had on IRC and the action I had in the March community call, I wanted to make a proposal related to the file format to track files. I am not yet submitting a fully formed patch as there may be differing opinions about the file format and name of the file

[Xen-devel] [ANNOUNCE] Xen Developer and Design Summit Program for 2019 is live

Dear Community Members, we are excited to unveil the Xen Project Developer and Design Summit program and speaker schedule [1]. The ​Xen Project ​Developer ​and ​Design ​Summit ​brings ​together ​the ​Xen ​Project’s ​community ​of ​developers ​and ​power ​users ​for ​their ​annual ​conference. ​

Re: [Xen-devel] [PATCH v2] docs/xl: Clarify documentation for mem-max and mem-set

On 13/05/2019, 08:28, "Wei Liu" wrote: On Mon, May 13, 2019 at 02:59:30PM +0100, Wei Liu wrote: > On Wed, May 01, 2019 at 03:59:41PM +0100, George Dunlap wrote: > > On 4/8/19 12:09 PM, George Dunlap wrote: > > > mem-set is the primary command that users will need to use and

Re: [Xen-devel] Criteria / validation proposal: drop Xen

Hi all, I am going to step in here with my hat as Xen Project community manager. We had a discussion about this issue as part of last week's community call. I CC'ed a number of stake-holders, which probably should have been on the thread such as ITL (which builds QubesOS on top of Fedora) and Mich

Re: [Xen-devel] Criteria / validation proposal: drop Xen

Apologies, I mixed up some references Lars > On 13 May 2019, at 16:29, Lars Kurth wrote: > > Hi all, > > I am going to step in here with my hat as Xen Project community > manager. We had a discussion about this issue as part of last week's > community call. I CC&#x

[Xen-devel] [PATCH] Add TRACKING.IMPORTS to xen.git to more easily manage imported files that need to be kept in sync with an upstream

committer looks at the diff and either - Decides to ignore it and bumps the commit ID in this file - Decides the change is needed, integrates it into Xen and then bumps the commit ID in this file Signed-off-by: Lars Kurth CC: committ...@xenproject.org --- TRACKING.IMPORTS | 40

Re: [Xen-devel] [PATCH] Add TRACKING.IMPORTS to xen.git to more easily manage imported files that need to be kept in sync with an upstream

On 16/05/2019, 04:47, "Jan Beulich" wrote: >>> On 16.05.19 at 00:18, wrote: > +# Mappings to track files are of the following format > +# --- > +# manual|auto xen-file name-of-original-repo original-file commit-id > +# >

Re: [Xen-devel] [PATCH] Add TRACKING.IMPORTS to xen.git to more easily manage imported files that need to be kept in sync with an upstream

On 17/05/2019, 01:34, "Jan Beulich" wrote: >>> On 16.05.19 at 17:54, wrote: > > On 16/05/2019, 04:47, "Jan Beulich" wrote: > > >>> On 16.05.19 at 00:18, wrote: > > +# Mappings to track files are of the following format > > +# --

Re: [Xen-devel] [PATCH] Add TRACKING.IMPORTS to xen.git to more easily manage imported files that need to be kept in sync with an upstream

On 20/05/2019, 10:37, "Ian Jackson" wrote: This is going in the right direction IMO. Lars Kurth writes ("Re: [PATCH] Add TRACKING.IMPORTS to xen.git to more easily manage imported files that need to be kept in sync with an upstream"): > That makes per

Re: [Xen-devel] Criteria / validation proposal: drop Xen

@Adam and Fedora Testing & QA: any views on my proposal? Regards Lars > On 13 May 2019, at 16:29, Lars Kurth wrote: > > Hi all, > > I am going to step in here with my hat as Xen Project community > manager. We had a discussion about this issue as part of last week's

[Xen-devel] [PATCH v2] Add TRACKING.IMPORTS to xen.git to more easily manage imported files that need to be kept in sync with an upstream

* Replace manual:|auto: with file: as there auto: use-case was invalid * Added more verbose description of format Signed-off-by: Lars Kurth CC: committ...@xenproject.org --- TRACKING.FILES | 50 ++ 1 file changed, 50 insertions(+) create mode 100644

Re: [Xen-devel] [PATCH v2] Add TRACKING.IMPORTS to xen.git to more easily manage imported files that need to be kept in sync with an upstream

On 24/05/2019, 05:24, "Jan Beulich" wrote: >>> On 24.05.19 at 03:36, wrote: > --- /dev/null > +++ b/TRACKING.FILES > @@ -0,0 +1,50 @@ > +# This file contains information about source files that have been > +# copied from other sources and need to be tracked > +#

[Xen-devel] [PATCH v3] Add TRACKING.IMPORTS to xen.git to more easily manage imported files that need to be kept in sync with an upstream

auto: use-case was invalid * Added more verbose description of format Changes since v2 * Changed some formatting * Removed examples * Removed references to https Signed-off-by: Lars Kurth CC: committ...@xenproject.org --- TRACKING.FILES | 44 1 file

Re: [Xen-devel] Guest Testing in OSSTEST - What distros and versions should we test against

> On 9 May 2019, at 19:43, Rich Persaud wrote: > > On May 9, 2019, at 21:28, Lars Kurth <mailto:lars.kurth@gmail.com>> wrote: > >> With regards to Windows testing we have some restrictions. We have tried >> several times to buy additional test licen

Re: [Xen-devel] Guest Testing in OSSTEST - What distros and versions should we test against

gt; On 9 May 2019, at 19:28, Lars Kurth wrote: > > Hi all, > > following a discussion with committers about Guest testing in OSSTEST, it > surfaced that we have not updated what distros we test in OSSTEST for a very > long time. All agreed that we should regularly review what we

[Xen-devel] Xen Project Community Call June 6th: @15:00 UTC Call for agenda items

Hi all, Please propose topics by either editing the running agenda document at https://cryptpad.fr/pad/#/2/pad/edit/WZr2VTdfmaPdvIxjXp+cgSF- or by replying to the mail. Ideally by Tuesday! Note that I am using another sharing mechanism as per request. Let me know if you have difficulties Best

Re: [Xen-devel] Xen Project Community Call June 6th: @15:00 UTC Call for agenda items

Hi all, a quick reminder that the call will be today Regards Lars On 30/05/2019, 18:35, "Lars Kurth" wrote: Hi all, Please propose topics by either editing the running agenda document at https://cryptpad.fr/pad/#/2/pad/edit/WZr2VTdfmaPdvIxjXp+cgSF- or by replying to

[Xen-devel] Xen (both x86 and Arm) Community Call: Jan 9 - 16:00 - 17:00 UTC - Call for Agenda Items

Hi all, based on Stefano's and Julien's suggestion that it may make sense to merge the x86 and arm calls, I am willing to try. It also makes sense this time in particular because we are approaching freeze time. As per request the meeting is 1 hour later than normal. Also, because there were N

Re: [Xen-devel] Xen (both x86 and Arm) Community Call: Jan 9 - 16:00 - 17:00 UTC - Call for Agenda Items

we won't be able to join. > > -- Artem > From: Stefano Stabellini <mailto:sstabell...@kernel.org>> > Sent: Thursday, January 3, 2019 7:17:02 PM > To: Lars Kurth > Cc: xen-devel; committ...@xenproject.org <mailto:committ...@xenproject.org>; >

Re: [Xen-devel] Xen (both x86 and Arm) Community Call: Jan 9 - 16:00 - 17:00 UTC - Call for Agenda Items

:33, Stefano Stabellini wrote: > > On Mon, 7 Jan 2019, Juergen Gross wrote: >> On 03/01/2019 15:28, Lars Kurth wrote: >>> Hi all, >>> >>> based on Stefano's and Julien's suggestion that it may make sense to merge >>> the x86 and arm call

Re: [Xen-devel] Xen (both x86 and Arm) Community Call: Jan 9 - 16:00 - 17:00 UTC - Call for Agenda Items

Hi all, I noticed that I hadn't updated all the times in the meeting invite block. > > == Dial-in Information == > > ## Future Community Call schedule > Jan 9, Feb 13, Mar 12 > > ## Meeting time > 15:00 - 16:00 UTC This is wrong and should read 16:00 - 17:00 >8:00 - 9:00 EDT (Sa

[Xen-devel] Organising a workshop to solve safety certification related questions

Hi all, just before XMas Stefano (Xilinx), Alex (EPAM), Artem (EPAM), Matt (Arm), Guilio (Xilinx) and Munakata San (Renesas) and me had a quick call see whether from a Xen Project community perspective, it would be possible to make significant progress towards making more easily Xen Safety cert

Re: [Xen-devel] Xen (both x86 and Arm) Community Call: Jan 9 - 16:00 - 17:00 UTC - Call for Agenda Items

Quick note: the meeting is in 15 minutes - the agenda is at https://docs.google.com/document/d/1Ufv9XcQO0zIAVeFbFCAHAeEIB9Ap4Y4srAm4vI8I01I/edit <https://docs.google.com/document/d/1Ufv9XcQO0zIAVeFbFCAHAeEIB9Ap4Y4srAm4vI8I01I/edit> > On 8 Jan 2019, at 14:34, Lars Kurth wrote: &g

[Xen-devel] Save the dates: Xen Project Developer Summit 2019 - July 9 -11, Chicago, IL, USA

Hi all, just a quick note to let you know that the next developer summit will be held in the US (in Chicago) from July 9-11. The event website including the CfP should be up in the next 2-3 weeks Best Regards Lars ___ Xen-devel mailing list Xen-devel@l

Re: [Xen-devel] [BUG] docs: our man page generation uses http://man.he.net/ by default which causes broken links. It should be changed to point to a relative path

Ping! Adding Ian Jackson specifically - we should really fix this for 4.12 Regards Lars > On 2 Aug 2018, at 12:24, Lars Kurth wrote: > > Hi all, > > most of our man pages on pretty much all releases from 4.2 contain broken > links. > > For example: > In https://xe

Re: [Xen-devel] Xen 4.12 Development Update

Hi Juergen, > On 14 Jan 2019, at 10:13, Juergen Gross wrote: > > This email only tracks big items for xen.git tree. Please reply for items you > would like to see in 4.12 so that people have an idea what is going on and > prioritise accordingly. > > You're welcome to provide description and use

Re: [Xen-devel] [PATCH v3 04/15] argo: init, destroy and soft-reset, with enable command line opt

Adding Juergen, to make sure he is aware of the discussion, as this is an excellent summary of the status of this series. > On 14 Jan 2019, at 14:46, Wei Liu wrote: > > Hi all > > The locking scheme seems to be remaining sticking point. The rest are > mostly cosmetic issues (FAOD, they still

[Xen-devel] Preparing for Xen Project GSoC applications : Deadline Feb 6

Hi all, I will be applying as a mentoring organisation for GSoC again this year: the application deadline is Feb 6 and by then we need to have https://wiki.xenproject.org/wiki/Outreach_Program_Projects in order. Given that we didn't get in last year, there is a 50/50 chance we get in this year

Re: [Xen-devel] [PATCH 2/2] docs: Fix links in html generation of man pages

> On 15 Jan 2019, at 17:07, Ian Jackson wrote: > > Anthony PERARD writes ("Re: [PATCH 2/2] docs: Fix links in html generation of > man pages"): snip > Anyway, this patch of yours is a big improvement, so: > > Acked-by: Ian Jackson > > I think linkifying that one missing link is a `nice to

Re: [Xen-devel] Organising a workshop to solve safety certification related questions

> On 16 Jan 2019, at 12:16, George Dunlap wrote: > > On 1/8/19 5:59 PM, Lars Kurth wrote: >> What I need is >> - Raise your hands if you are interested >> - Let me know of date / location restrictions >> - We could try and so some of this via video conference

Re: [Xen-devel] Preparing for Xen Project GSoC applications : Deadline Feb 6

====== > Registered at Amtsgericht Mannheim, Germany, HRB728558 > > On 15.01.19, 14:33, "Lars Kurth" wrote: > >Hi all, > >I will be applying as a mentoring organisation for GSoC again this year: > the application deadline is Feb 6 and

Re: [Xen-devel] Organising a workshop to solve safety certification related questions

work on the agenda. Best Regards Lars > On 16 Jan 2019, at 13:09, Lars Kurth wrote: > > > >> On 16 Jan 2019, at 12:16, George Dunlap > <mailto:george.dun...@citrix.com>> wrote: >> >> On 1/8/19 5:59 PM, Lars Kurth wrote: >>> What I need is >

[Xen-devel] Xen Project Developer and Design Summit 2019: Cfp and Registration Open Now

Dear Community Members, starting today, registration officially opens for The Xen Project Developer & Design Summit. This year’s Summit, taking place from July 9 through 11 in Chicago, will bring together the Xen Project community of developers and power users to share ideas, latest development

Re: [Xen-devel] [PATCH] tboot: remove maintainers and declare orphaned

> On 26 Jul 2019, at 08:17, Roger Pau Monné wrote: > > On Thu, Jul 25, 2019 at 03:08:07PM -0400, Rich Persaud wrote: >> (cc Intel and tboot-devel) >> >> Hi Roger, >> >> Thanks for your interest in documenting the status of maintenance for Intel >> TXT support in Xen. Intel TXT and Xen are d

Re: [Xen-devel] [RFC] xen: Add .astylerc for automated style-formatting

On 26/07/2019, 16:12, "Julien Grall" wrote: Hi Viktor, On 26/07/2019 15:58, Viktor Mitin wrote: > On Fri, Jul 19, 2019 at 11:37 AM Julien Grall wrote: >> >> Hi Tamas, >> >> On 18/07/2019 18:22, Tamas K Lengyel wrote: - Line 139: The { are common

Re: [Xen-devel] [RFC] XCP-ng subproject proposal

Hi everyone, adding committers, who would need to vote for or against the proposal. The title probably does not need an RFC, which is why no-one looked at it so far I think this is a great idea and I would want to welcome XCP-ng into the project: with this in mind, I vote +1 Lars > On 22 Jul

Re: [Xen-devel] [PATCH] Intel TXT: add reviewer, move to Odd Fixes state

> On 30 Jul 2019, at 11:08, George Dunlap wrote: > > On 7/30/19 10:54 AM, Julien Grall wrote: >> Hi Jan, >> >> On 30/07/2019 10:05, Jan Beulich wrote: >>> On 30.07.2019 10:54, Julien Grall wrote: On 7/30/19 9:29 AM, Jan Beulich wrote: > On 30.07.2019 08:56, Lukasz Hawrylko wrote:

[Xen-devel] [ANNOUNCE} Call for agenda items for Aug 1st Community Call @ 15:00 UTC

Hi all, the proposed agenda is in https://cryptpad.fr/pad/#/2/pad/edit/arfa2Pr3D2uIuEN3EWNTdOVT/ Alternatively, you can reply to this mail directly Agenda items appreciated by tomorrow Regards Lars P.S.: If you want to be added or removed from the CC list please reply privately == Dial-in Informa

Re: [Xen-devel] [PATCH] Intel TXT: add reviewer, move to Odd Fixes state

> On 31 Jul 2019, at 12:52, Julien Grall wrote: > >> To move forward: >> * There should be a policy discussion > > How should I raise it? Do you want a patch again contribution-guidelines? I think we should start with an e-mail thread with an appropriate title on xen-devel@ (CCing committers

Re: [Xen-devel] Xen Coding style and clang-format

> On 31 Jul 2019, at 12:43, Viktor Mitin wrote: > > On Wed, Jul 31, 2019 at 2:25 PM Julien Grall > wrote: >> >> >> >> On 31/07/2019 12:16, Viktor Mitin wrote: >>> On Mon, Jul 29, 2019 at 3:35 PM Julien Grall wrote: On 7/29/19 1:21 PM, Viktor Mitin wrote: >

Re: [Xen-devel] [PATCH] CODING_STYLE: clarify function argument indentation

> On 31 Jul 2019, at 17:54, Viktor Mitin wrote: > > Hi All, > > On Wed, Jul 31, 2019 at 7:45 PM Andrew Cooper > wrote: >> >> On 31/07/2019 17:24, Volodymyr Babchuk wrote: >>> There are coding style rules that are widely accepted by community, >>> but newer were formalized in the document. N

  1   2   3   4   5   >